diff --git a/package-lock.json b/package-lock.json index df5662d..754ef93 100644 --- a/package-lock.json +++ b/package-lock.json @@ -13,7 +13,7 @@ "deep-equal": "^2.0.5", "github-enterprise-server-versions": "^2.0.1", "lodash": "^4.17.21", - "openapi-typescript": "^6.2.1", + "openapi-typescript": "^7.0.0", "prettier": "^3.0.0", "semantic-release-plugin-update-version-in-files": "^1.1.0" }, @@ -21,48 +21,182 @@ "node": ">=20" } }, - "node_modules/@fastify/busboy": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/@fastify/busboy/-/busboy-2.1.0.tgz", - "integrity": "sha512-+KpH+QxZU7O4675t3mnkQKcZZg56u+K/Ct2K+N2AZYNVK8kyeo/bI18tI8aPm3tvNNRyTWfj6s5tnGNlcbQRsA==", + "node_modules/@babel/code-frame": { + "version": "7.22.13", + "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.22.13.tgz", + "integrity": "sha512-XktuhWlJ5g+3TJXc5upd9Ks1HutSArik6jf2eAjYFyIOf4ej3RN+184cZbzDvbPnuTJIUhPKKJE3cIsYTiAT3w==", "dev": true, + "dependencies": { + "@babel/highlight": "^7.22.13", + "chalk": "^2.4.2" + }, "engines": { - "node": ">=14" + "node": ">=6.9.0" } }, - "node_modules/@nodelib/fs.scandir": { - "version": "2.1.5", - "resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz", - "integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==", + "node_modules/@babel/code-frame/node_modules/ansi-styles": { + "version": "3.2.1", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz", + "integrity": "sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==", "dev": true, "dependencies": { - "@nodelib/fs.stat": "2.0.5", - "run-parallel": "^1.1.9" + "color-convert": "^1.9.0" }, "engines": { - "node": ">= 8" + "node": ">=4" } }, - "node_modules/@nodelib/fs.stat": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz", - "integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==", + "node_modules/@babel/code-frame/node_modules/chalk": { + "version": "2.4.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.2.tgz", + "integrity": "sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==", + "dev": true, + "dependencies": { + "ansi-styles": "^3.2.1", + "escape-string-regexp": "^1.0.5", + "supports-color": "^5.3.0" + }, + "engines": { + "node": ">=4" + } + }, + "node_modules/@babel/code-frame/node_modules/color-convert": { + "version": "1.9.3", + "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-1.9.3.tgz", + "integrity": "sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==", + "dev": true, + "dependencies": { + "color-name": "1.1.3" + } + }, + "node_modules/@babel/code-frame/node_modules/color-name": { + "version": "1.1.3", + "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz", + "integrity": "sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==", + "dev": true + }, + "node_modules/@babel/code-frame/node_modules/escape-string-regexp": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz", + "integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==", + "dev": true, + "engines": { + "node": ">=0.8.0" + } + }, + "node_modules/@babel/code-frame/node_modules/has-flag": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz", + "integrity": "sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==", + "dev": true, + "engines": { + "node": ">=4" + } + }, + "node_modules/@babel/code-frame/node_modules/supports-color": { + "version": "5.5.0", + "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz", + "integrity": "sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==", + "dev": true, + "dependencies": { + "has-flag": "^3.0.0" + }, + "engines": { + "node": ">=4" + } + }, + "node_modules/@babel/helper-validator-identifier": { + "version": "7.22.20", + "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.22.20.tgz", + "integrity": "sha512-Y4OZ+ytlatR8AI+8KZfKuL5urKp7qey08ha31L8b3BwewJAoJamTzyvxPR/5D+KkdJCGPq/+8TukHBlY10FX9A==", + "dev": true, + "engines": { + "node": ">=6.9.0" + } + }, + "node_modules/@babel/highlight": { + "version": "7.22.20", + "resolved": "https://registry.npmjs.org/@babel/highlight/-/highlight-7.22.20.tgz", + "integrity": "sha512-dkdMCN3py0+ksCgYmGG8jKeGA/8Tk+gJwSYYlFGxG5lmhfKNoAy004YpLxpS1W2J8m/EK2Ew+yOs9pVRwO89mg==", + "dev": true, + "dependencies": { + "@babel/helper-validator-identifier": "^7.22.20", + "chalk": "^2.4.2", + "js-tokens": "^4.0.0" + }, + "engines": { + "node": ">=6.9.0" + } + }, + "node_modules/@babel/highlight/node_modules/ansi-styles": { + "version": "3.2.1", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz", + "integrity": "sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==", + "dev": true, + "dependencies": { + "color-convert": "^1.9.0" + }, + "engines": { + "node": ">=4" + } + }, + "node_modules/@babel/highlight/node_modules/chalk": { + "version": "2.4.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.2.tgz", + "integrity": "sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==", "dev": true, + "dependencies": { + "ansi-styles": "^3.2.1", + "escape-string-regexp": "^1.0.5", + "supports-color": "^5.3.0" + }, "engines": { - "node": ">= 8" + "node": ">=4" } }, - "node_modules/@nodelib/fs.walk": { - "version": "1.2.8", - "resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz", - "integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==", + "node_modules/@babel/highlight/node_modules/color-convert": { + "version": "1.9.3", + "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-1.9.3.tgz", + "integrity": "sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==", "dev": true, "dependencies": { - "@nodelib/fs.scandir": "2.1.5", - "fastq": "^1.6.0" + "color-name": "1.1.3" + } + }, + "node_modules/@babel/highlight/node_modules/color-name": { + "version": "1.1.3", + "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz", + "integrity": "sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==", + "dev": true + }, + "node_modules/@babel/highlight/node_modules/escape-string-regexp": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz", + "integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==", + "dev": true, + "engines": { + "node": ">=0.8.0" + } + }, + "node_modules/@babel/highlight/node_modules/has-flag": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz", + "integrity": "sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==", + "dev": true, + "engines": { + "node": ">=4" + } + }, + "node_modules/@babel/highlight/node_modules/supports-color": { + "version": "5.5.0", + "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz", + "integrity": "sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==", + "dev": true, + "dependencies": { + "has-flag": "^3.0.0" }, "engines": { - "node": ">= 8" + "node": ">=4" } }, "node_modules/@octokit/auth-token": { @@ -94,6 +228,36 @@ "node": ">= 18" } }, + "node_modules/@octokit/core/node_modules/@octokit/openapi-types": { + "version": "22.2.0", + "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-22.2.0.tgz", + "integrity": "sha512-QBhVjcUa9W7Wwhm6DBFu6ZZ+1/t/oYxqc2tp81Pi41YNuJinbFRx8B133qVOrAaBbF7D/m0Et6f9/pZt9Rc+tg==", + "dev": true, + "license": "MIT" + }, + "node_modules/@octokit/core/node_modules/@octokit/request-error": { + "version": "6.1.5", + "resolved": "https://registry.npmjs.org/@octokit/request-error/-/request-error-6.1.5.tgz", + "integrity": "sha512-IlBTfGX8Yn/oFPMwSfvugfncK2EwRLjzbrpifNaMY8o/HTEAFqCA1FZxjD9cWvSKBHgrIhc4CSBIzMxiLsbzFQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "@octokit/types": "^13.0.0" + }, + "engines": { + "node": ">= 18" + } + }, + "node_modules/@octokit/core/node_modules/@octokit/types": { + "version": "13.6.1", + "resolved": "https://registry.npmjs.org/@octokit/types/-/types-13.6.1.tgz", + "integrity": "sha512-PHZE9Z+kWXb23Ndik8MKPirBPziOc0D2/3KH1P+6jK5nGWe96kadZuE4jev2/Jq7FvIfTlT2Ltg8Fv2x1v0a5g==", + "dev": true, + "license": "MIT", + "dependencies": { + "@octokit/openapi-types": "^22.2.0" + } + }, "node_modules/@octokit/endpoint": { "version": "10.1.1", "resolved": "https://registry.npmjs.org/@octokit/endpoint/-/endpoint-10.1.1.tgz", @@ -108,6 +272,23 @@ "node": ">= 18" } }, + "node_modules/@octokit/endpoint/node_modules/@octokit/openapi-types": { + "version": "22.2.0", + "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-22.2.0.tgz", + "integrity": "sha512-QBhVjcUa9W7Wwhm6DBFu6ZZ+1/t/oYxqc2tp81Pi41YNuJinbFRx8B133qVOrAaBbF7D/m0Et6f9/pZt9Rc+tg==", + "dev": true, + "license": "MIT" + }, + "node_modules/@octokit/endpoint/node_modules/@octokit/types": { + "version": "13.6.1", + "resolved": "https://registry.npmjs.org/@octokit/types/-/types-13.6.1.tgz", + "integrity": "sha512-PHZE9Z+kWXb23Ndik8MKPirBPziOc0D2/3KH1P+6jK5nGWe96kadZuE4jev2/Jq7FvIfTlT2Ltg8Fv2x1v0a5g==", + "dev": true, + "license": "MIT", + "dependencies": { + "@octokit/openapi-types": "^22.2.0" + } + }, "node_modules/@octokit/graphql": { "version": "8.1.1", "resolved": "https://registry.npmjs.org/@octokit/graphql/-/graphql-8.1.1.tgz", @@ -123,13 +304,23 @@ "node": ">= 18" } }, - "node_modules/@octokit/openapi-types": { + "node_modules/@octokit/graphql/node_modules/@octokit/openapi-types": { "version": "22.2.0", "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-22.2.0.tgz", "integrity": "sha512-QBhVjcUa9W7Wwhm6DBFu6ZZ+1/t/oYxqc2tp81Pi41YNuJinbFRx8B133qVOrAaBbF7D/m0Et6f9/pZt9Rc+tg==", "dev": true, "license": "MIT" }, + "node_modules/@octokit/graphql/node_modules/@octokit/types": { + "version": "13.6.1", + "resolved": "https://registry.npmjs.org/@octokit/types/-/types-13.6.1.tgz", + "integrity": "sha512-PHZE9Z+kWXb23Ndik8MKPirBPziOc0D2/3KH1P+6jK5nGWe96kadZuE4jev2/Jq7FvIfTlT2Ltg8Fv2x1v0a5g==", + "dev": true, + "license": "MIT", + "dependencies": { + "@octokit/openapi-types": "^22.2.0" + } + }, "node_modules/@octokit/request": { "version": "9.1.3", "resolved": "https://registry.npmjs.org/@octokit/request/-/request-9.1.3.tgz", @@ -146,7 +337,14 @@ "node": ">= 18" } }, - "node_modules/@octokit/request-error": { + "node_modules/@octokit/request/node_modules/@octokit/openapi-types": { + "version": "22.2.0", + "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-22.2.0.tgz", + "integrity": "sha512-QBhVjcUa9W7Wwhm6DBFu6ZZ+1/t/oYxqc2tp81Pi41YNuJinbFRx8B133qVOrAaBbF7D/m0Et6f9/pZt9Rc+tg==", + "dev": true, + "license": "MIT" + }, + "node_modules/@octokit/request/node_modules/@octokit/request-error": { "version": "6.1.5", "resolved": "https://registry.npmjs.org/@octokit/request-error/-/request-error-6.1.5.tgz", "integrity": "sha512-IlBTfGX8Yn/oFPMwSfvugfncK2EwRLjzbrpifNaMY8o/HTEAFqCA1FZxjD9cWvSKBHgrIhc4CSBIzMxiLsbzFQ==", @@ -159,7 +357,7 @@ "node": ">= 18" } }, - "node_modules/@octokit/types": { + "node_modules/@octokit/request/node_modules/@octokit/types": { "version": "13.6.1", "resolved": "https://registry.npmjs.org/@octokit/types/-/types-13.6.1.tgz", "integrity": "sha512-PHZE9Z+kWXb23Ndik8MKPirBPziOc0D2/3KH1P+6jK5nGWe96kadZuE4jev2/Jq7FvIfTlT2Ltg8Fv2x1v0a5g==", @@ -169,6 +367,89 @@ "@octokit/openapi-types": "^22.2.0" } }, + "node_modules/@redocly/ajv": { + "version": "8.11.2", + "resolved": "https://registry.npmjs.org/@redocly/ajv/-/ajv-8.11.2.tgz", + "integrity": "sha512-io1JpnwtIcvojV7QKDUSIuMN/ikdOUd1ReEnUnMKGfDVridQZ31J0MmIuqwuRjWDZfmvr+Q0MqCcfHM2gTivOg==", + "dev": true, + "license": "MIT", + "dependencies": { + "fast-deep-equal": "^3.1.1", + "json-schema-traverse": "^1.0.0", + "require-from-string": "^2.0.2", + "uri-js-replace": "^1.0.1" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/epoberezkin" + } + }, + "node_modules/@redocly/config": { + "version": "0.16.0", + "resolved": "https://registry.npmjs.org/@redocly/config/-/config-0.16.0.tgz", + "integrity": "sha512-t9jnODbUcuANRSl/K4L9nb12V+U5acIHnVSl26NWrtSdDZVtoqUXk2yGFPZzohYf62cCfEQUT8ouJ3bhPfpnJg==", + "dev": true, + "license": "MIT" + }, + "node_modules/@redocly/openapi-core": { + "version": "1.25.12", + "resolved": "https://registry.npmjs.org/@redocly/openapi-core/-/openapi-core-1.25.12.tgz", + "integrity": "sha512-DyIZJccysDVOTcdamBeIwi/0Ffn7+UazfQYFM0hPgrEq6oXzrbE+FhyF5m0ykAUB8PNsYcK7Z4ATg1JxR+QP2Q==", + "dev": true, + "license": "MIT", + "dependencies": { + "@redocly/ajv": "^8.11.2", + "@redocly/config": "^0.16.0", + "colorette": "^1.2.0", + "https-proxy-agent": "^7.0.4", + "js-levenshtein": "^1.1.6", + "js-yaml": "^4.1.0", + "lodash.isequal": "^4.5.0", + "minimatch": "^5.0.1", + "node-fetch": "^2.6.1", + "pluralize": "^8.0.0", + "yaml-ast-parser": "0.0.43" + }, + "engines": { + "node": ">=14.19.0", + "npm": ">=7.0.0" + } + }, + "node_modules/@redocly/openapi-core/node_modules/brace-expansion": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.1.tgz", + "integrity": "sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==", + "dev": true, + "license": "MIT", + "dependencies": { + "balanced-match": "^1.0.0" + } + }, + "node_modules/@redocly/openapi-core/node_modules/minimatch": { + "version": "5.1.6", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-5.1.6.tgz", + "integrity": "sha512-lKwV/1brpG6mBUFHtb7NUmtABCb2WZZmm2wNiOA5hAb8VdCS4B3dtMWyvcoViccwAW/COERjXLt0zP1zXUN26g==", + "dev": true, + "license": "ISC", + "dependencies": { + "brace-expansion": "^2.0.1" + }, + "engines": { + "node": ">=10" + } + }, + "node_modules/agent-base": { + "version": "7.1.0", + "resolved": "https://registry.npmjs.org/agent-base/-/agent-base-7.1.0.tgz", + "integrity": "sha512-o/zjMZRhJxny7OyEF+Op8X+efiELC7k7yOjMzgfzVqOzXqkBkWI79YoTdOtsuWd5BWhAGAuOY/Xa6xpiaWXiNg==", + "dev": true, + "dependencies": { + "debug": "^4.3.4" + }, + "engines": { + "node": ">= 14" + } + }, "node_modules/ansi-colors": { "version": "4.1.3", "resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-4.1.3.tgz", @@ -185,25 +466,22 @@ "dev": true }, "node_modules/array-buffer-byte-length": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/array-buffer-byte-length/-/array-buffer-byte-length-1.0.1.tgz", - "integrity": "sha512-ahC5W1xgou+KTXix4sAO8Ki12Q+jf4i0+tmk3sC+zgcynshkHxzpXdImBehiUYKKKDwvfFiJl1tZt6ewscS1Mg==", + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/array-buffer-byte-length/-/array-buffer-byte-length-1.0.0.tgz", + "integrity": "sha512-LPuwb2P+NrQw3XhxGc36+XSvuBPopovXYTR9Ew++Du9Yb/bx5AzBfrIsBoj0EZUifjQU+sHL21sseZ3jerWO/A==", "dev": true, "dependencies": { - "call-bind": "^1.0.5", - "is-array-buffer": "^3.0.4" - }, - "engines": { - "node": ">= 0.4" + "call-bind": "^1.0.2", + "is-array-buffer": "^3.0.1" }, "funding": { "url": "https://github.com/sponsors/ljharb" } }, "node_modules/available-typed-arrays": { - "version": "1.0.6", - "resolved": "https://registry.npmjs.org/available-typed-arrays/-/available-typed-arrays-1.0.6.tgz", - "integrity": "sha512-j1QzY8iPNPG4o4xmO3ptzpRxTciqD3MgEHtifP/YnJpIo58Xu+ne4BejlbkuaLfXn/nz6HFiw29bLpj2PNMdGg==", + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/available-typed-arrays/-/available-typed-arrays-1.0.5.tgz", + "integrity": "sha512-DMD0KiN46eipeziST1LPP/STfDU0sufISXmjSgvVsoU2tqxctQeASejWcfNtxYKqETM1UxQ8sp2OrSBWpHY6sw==", "dev": true, "engines": { "node": ">= 0.4" @@ -235,36 +513,33 @@ "concat-map": "0.0.1" } }, - "node_modules/braces": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/braces/-/braces-3.0.3.tgz", - "integrity": "sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==", - "dev": true, - "dependencies": { - "fill-range": "^7.1.1" - }, - "engines": { - "node": ">=8" - } - }, "node_modules/call-bind": { - "version": "1.0.6", - "resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.6.tgz", - "integrity": "sha512-Mj50FLHtlsoVfRfnHaZvyrooHcrlceNZdL/QBvJJVd9Ta55qCQK0gs4ss2oZDeV9zFCs6ewzYgVE5yfVmfFpVg==", + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.2.tgz", + "integrity": "sha512-7O+FbCihrB5WGbFYesctwmTKae6rOiIzmz1icreWJ+0aA7LJfuqhEso2T9ncpcFtzMQtzXf2QGGueWJGTYsqrA==", "dev": true, "dependencies": { - "es-errors": "^1.3.0", - "function-bind": "^1.1.2", - "get-intrinsic": "^1.2.3", - "set-function-length": "^1.2.0" - }, - "engines": { - "node": ">= 0.4" + "function-bind": "^1.1.1", + "get-intrinsic": "^1.0.2" }, "funding": { "url": "https://github.com/sponsors/ljharb" } }, + "node_modules/change-case": { + "version": "5.4.4", + "resolved": "https://registry.npmjs.org/change-case/-/change-case-5.4.4.tgz", + "integrity": "sha512-HRQyTk2/YPEkt9TnUPbOpr64Uw3KOicFWPVBb+xiHvd6eBx/qPr9xqfBFDT8P2vWsvvz4jbEkfDe71W3VyNu2w==", + "dev": true, + "license": "MIT" + }, + "node_modules/colorette": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/colorette/-/colorette-1.4.0.tgz", + "integrity": "sha512-Y2oEozpomLn7Q3HFP7dpww7AtMJplbM9lGZP6RDfHqmbeRjiwRg4n6VM6j4KLmRke85uWEI7JqF17f3pqdRA0g==", + "dev": true, + "license": "MIT" + }, "node_modules/concat-map": { "version": "0.0.1", "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz", @@ -289,15 +564,15 @@ } }, "node_modules/deep-equal": { - "version": "2.2.3", - "resolved": "https://registry.npmjs.org/deep-equal/-/deep-equal-2.2.3.tgz", - "integrity": "sha512-ZIwpnevOurS8bpT4192sqAowWM76JDKSHYzMLty3BZGSswgq6pBaH3DhCSW5xVAZICZyKdOBPjwww5wfgT/6PA==", + "version": "2.2.2", + "resolved": "https://registry.npmjs.org/deep-equal/-/deep-equal-2.2.2.tgz", + "integrity": "sha512-xjVyBf0w5vH0I42jdAZzOKVldmPgSulmiyPRywoyq7HXC9qdgo17kxJE+rdnif5Tz6+pIrpJI8dCpMNLIGkUiA==", "dev": true, "dependencies": { "array-buffer-byte-length": "^1.0.0", - "call-bind": "^1.0.5", + "call-bind": "^1.0.2", "es-get-iterator": "^1.1.3", - "get-intrinsic": "^1.2.2", + "get-intrinsic": "^1.2.1", "is-arguments": "^1.1.1", "is-array-buffer": "^3.0.2", "is-date-object": "^1.0.5", @@ -307,29 +582,25 @@ "object-is": "^1.1.5", "object-keys": "^1.1.1", "object.assign": "^4.1.4", - "regexp.prototype.flags": "^1.5.1", + "regexp.prototype.flags": "^1.5.0", "side-channel": "^1.0.4", "which-boxed-primitive": "^1.0.2", "which-collection": "^1.0.1", - "which-typed-array": "^1.1.13" - }, - "engines": { - "node": ">= 0.4" + "which-typed-array": "^1.1.9" }, "funding": { "url": "https://github.com/sponsors/ljharb" } }, "node_modules/define-data-property": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/define-data-property/-/define-data-property-1.1.2.tgz", - "integrity": "sha512-SRtsSqsDbgpJBbW3pABMCOt6rQyeM8s8RiyeSN8jYG8sYmt/kGJejbydttUsnDs1tadr19tvhT4ShwMyoqAm4g==", + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/define-data-property/-/define-data-property-1.1.1.tgz", + "integrity": "sha512-E7uGkTzkk1d0ByLeSc6ZsFS79Axg+m1P/VsgYsxHgiuc3tFSj+MjMIwe90FC4lOAZzNBdY7kkO2P2wKdsQ1vgQ==", "dev": true, "dependencies": { - "es-errors": "^1.3.0", - "get-intrinsic": "^1.2.2", + "get-intrinsic": "^1.2.1", "gopd": "^1.0.1", - "has-property-descriptors": "^1.0.1" + "has-property-descriptors": "^1.0.0" }, "engines": { "node": ">= 0.4" @@ -352,15 +623,6 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/es-errors": { - "version": "1.3.0", - "resolved": "https://registry.npmjs.org/es-errors/-/es-errors-1.3.0.tgz", - "integrity": "sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==", - "dev": true, - "engines": { - "node": ">= 0.4" - } - }, "node_modules/es-get-iterator": { "version": "1.1.3", "resolved": "https://registry.npmjs.org/es-get-iterator/-/es-get-iterator-1.1.3.tgz", @@ -381,42 +643,12 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/fast-glob": { - "version": "3.3.2", - "resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.2.tgz", - "integrity": "sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==", - "dev": true, - "dependencies": { - "@nodelib/fs.stat": "^2.0.2", - "@nodelib/fs.walk": "^1.2.3", - "glob-parent": "^5.1.2", - "merge2": "^1.3.0", - "micromatch": "^4.0.4" - }, - "engines": { - "node": ">=8.6.0" - } - }, - "node_modules/fastq": { - "version": "1.17.1", - "resolved": "https://registry.npmjs.org/fastq/-/fastq-1.17.1.tgz", - "integrity": "sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==", - "dev": true, - "dependencies": { - "reusify": "^1.0.4" - } - }, - "node_modules/fill-range": { - "version": "7.1.1", - "resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.1.1.tgz", - "integrity": "sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==", + "node_modules/fast-deep-equal": { + "version": "3.1.3", + "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", + "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==", "dev": true, - "dependencies": { - "to-regex-range": "^5.0.1" - }, - "engines": { - "node": ">=8" - } + "license": "MIT" }, "node_modules/for-each": { "version": "0.3.3", @@ -452,19 +684,15 @@ } }, "node_modules/get-intrinsic": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.2.4.tgz", - "integrity": "sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ==", + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.2.1.tgz", + "integrity": "sha512-2DcsyfABl+gVHEfCOaTrWgyt+tb6MSEGmKq+kI5HwLbIYgjgmMcV8KQ41uaKz1xxUcn9tJtgFbQUEVcEbd0FYw==", "dev": true, "dependencies": { - "es-errors": "^1.3.0", - "function-bind": "^1.1.2", + "function-bind": "^1.1.1", + "has": "^1.0.3", "has-proto": "^1.0.1", - "has-symbols": "^1.0.3", - "hasown": "^2.0.0" - }, - "engines": { - "node": ">= 0.4" + "has-symbols": "^1.0.3" }, "funding": { "url": "https://github.com/sponsors/ljharb" @@ -499,18 +727,6 @@ "url": "https://github.com/sponsors/isaacs" } }, - "node_modules/glob-parent": { - "version": "5.1.2", - "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz", - "integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==", - "dev": true, - "dependencies": { - "is-glob": "^4.0.1" - }, - "engines": { - "node": ">= 6" - } - }, "node_modules/gopd": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/gopd/-/gopd-1.0.1.tgz", @@ -523,6 +739,15 @@ "url": "https://github.com/sponsors/ljharb" } }, + "node_modules/has": { + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/has/-/has-1.0.4.tgz", + "integrity": "sha512-qdSAmqLF6209RFj4VVItywPMbm3vWylknmB3nvNiUIs72xAimcM8nVYxYr7ncvZq5qzk9MKIZR8ijqD/1QuYjQ==", + "dev": true, + "engines": { + "node": ">= 0.4.0" + } + }, "node_modules/has-bigints": { "version": "1.0.2", "resolved": "https://registry.npmjs.org/has-bigints/-/has-bigints-1.0.2.tgz", @@ -533,12 +758,12 @@ } }, "node_modules/has-property-descriptors": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.1.tgz", - "integrity": "sha512-VsX8eaIewvas0xnvinAe9bw4WfIeODpGYikiWYLH+dma0Jw6KHYqWiWfhQlgOVK8D6PvjubK5Uc4P0iIhIcNVg==", + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.0.tgz", + "integrity": "sha512-62DVLZGoiEBDHQyqG4w9xCuZ7eJEwNmJRWw2VY84Oedb7WFcA27fiEVe8oUQx9hAUJ4ekurquucTGwsyO1XGdQ==", "dev": true, "dependencies": { - "get-intrinsic": "^1.2.2" + "get-intrinsic": "^1.1.1" }, "funding": { "url": "https://github.com/sponsors/ljharb" @@ -569,12 +794,12 @@ } }, "node_modules/has-tostringtag": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.2.tgz", - "integrity": "sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==", + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.0.tgz", + "integrity": "sha512-kFjcSNhnlGV1kyoGk7OXKSawH5JOb/LzUc5w9B02hOTO0dfFRjbHQKvg1d6cf3HbeUmtU9VbbV3qzZ2Teh97WQ==", "dev": true, "dependencies": { - "has-symbols": "^1.0.3" + "has-symbols": "^1.0.2" }, "engines": { "node": ">= 0.4" @@ -583,16 +808,31 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/hasown": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.1.tgz", - "integrity": "sha512-1/th4MHjnwncwXsIW6QMzlvYL9kG5e/CpVvLRZe4XPa8TOUNbCELqmvhDmnkNsAjwaG4+I8gJJL0JBvTTLO9qA==", + "node_modules/https-proxy-agent": { + "version": "7.0.5", + "resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-7.0.5.tgz", + "integrity": "sha512-1e4Wqeblerz+tMKPIq2EMGiiWW1dIjZOksyHWSUm1rmuvw/how9hBHZ38lAGj5ID4Ik6EdkOw7NmWPy6LAwalw==", "dev": true, + "license": "MIT", "dependencies": { - "function-bind": "^1.1.2" + "agent-base": "^7.0.2", + "debug": "4" }, "engines": { - "node": ">= 0.4" + "node": ">= 14" + } + }, + "node_modules/index-to-position": { + "version": "0.1.2", + "resolved": "https://registry.npmjs.org/index-to-position/-/index-to-position-0.1.2.tgz", + "integrity": "sha512-MWDKS3AS1bGCHLBA2VLImJz42f7bJh8wQsTGCzI3j519/CASStoDONUBVz2I/VID0MpiX3SGSnbOD2xUalbE5g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" } }, "node_modules/inflight": { @@ -612,13 +852,13 @@ "dev": true }, "node_modules/internal-slot": { - "version": "1.0.7", - "resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.7.tgz", - "integrity": "sha512-NGnrKwXzSms2qUUih/ILZ5JBqNTSa1+ZmP6flaIp6KmSElgE9qdndzS3cqjrDovwFdmwsGsLdeFgB6suw+1e9g==", + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.5.tgz", + "integrity": "sha512-Y+R5hJrzs52QCG2laLn4udYVnxsfny9CpOhNhUvk/SSSVyF6T27FzRbF0sroPidSu3X8oEAkOn2K804mjpt6UQ==", "dev": true, "dependencies": { - "es-errors": "^1.3.0", - "hasown": "^2.0.0", + "get-intrinsic": "^1.2.0", + "has": "^1.0.3", "side-channel": "^1.0.4" }, "engines": { @@ -642,16 +882,14 @@ } }, "node_modules/is-array-buffer": { - "version": "3.0.4", - "resolved": "https://registry.npmjs.org/is-array-buffer/-/is-array-buffer-3.0.4.tgz", - "integrity": "sha512-wcjaerHw0ydZwfhiKbXJWLDY8A7yV7KhjQOpb83hGgGfId/aQa4TOvwyzn2PuswW2gPCYEL/nEAiSVpdOj1lXw==", + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/is-array-buffer/-/is-array-buffer-3.0.2.tgz", + "integrity": "sha512-y+FyyR/w8vfIRq4eQcM1EYgSTnmHXPqaF+IgzgraytCFq5Xh8lllDVmAZolPJiZttZLeFSINPYMaEJ7/vWUa1w==", "dev": true, "dependencies": { "call-bind": "^1.0.2", - "get-intrinsic": "^1.2.1" - }, - "engines": { - "node": ">= 0.4" + "get-intrinsic": "^1.2.0", + "is-typed-array": "^1.1.10" }, "funding": { "url": "https://github.com/sponsors/ljharb" @@ -712,27 +950,6 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/is-extglob": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz", - "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==", - "dev": true, - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/is-glob": { - "version": "4.0.3", - "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz", - "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==", - "dev": true, - "dependencies": { - "is-extglob": "^2.1.1" - }, - "engines": { - "node": ">=0.10.0" - } - }, "node_modules/is-map": { "version": "2.0.2", "resolved": "https://registry.npmjs.org/is-map/-/is-map-2.0.2.tgz", @@ -742,15 +959,6 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/is-number": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz", - "integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==", - "dev": true, - "engines": { - "node": ">=0.12.0" - } - }, "node_modules/is-number-object": { "version": "1.0.7", "resolved": "https://registry.npmjs.org/is-number-object/-/is-number-object-1.0.7.tgz", @@ -833,6 +1041,21 @@ "url": "https://github.com/sponsors/ljharb" } }, + "node_modules/is-typed-array": { + "version": "1.1.12", + "resolved": "https://registry.npmjs.org/is-typed-array/-/is-typed-array-1.1.12.tgz", + "integrity": "sha512-Z14TF2JNG8Lss5/HMqt0//T9JeHXttXy5pH/DBU4vi98ozO2btxzq9MwYDZYnKwU8nRsz/+GVFVRDq3DkVuSPg==", + "dev": true, + "dependencies": { + "which-typed-array": "^1.1.11" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, "node_modules/is-weakmap": { "version": "2.0.1", "resolved": "https://registry.npmjs.org/is-weakmap/-/is-weakmap-2.0.1.tgz", @@ -861,6 +1084,22 @@ "integrity": "sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==", "dev": true }, + "node_modules/js-levenshtein": { + "version": "1.1.6", + "resolved": "https://registry.npmjs.org/js-levenshtein/-/js-levenshtein-1.1.6.tgz", + "integrity": "sha512-X2BB11YZtrRqY4EnQcLX5Rh373zbK4alC1FW7D7MBhL2gtcC17cTnr6DmfHZeS0s2rTHjUTMMHfG7gO8SSdw+g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/js-tokens": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz", + "integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==", + "dev": true + }, "node_modules/js-yaml": { "version": "4.1.0", "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz", @@ -873,33 +1112,25 @@ "js-yaml": "bin/js-yaml.js" } }, + "node_modules/json-schema-traverse": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz", + "integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==", + "dev": true, + "license": "MIT" + }, "node_modules/lodash": { "version": "4.17.21", "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz", "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==", "dev": true }, - "node_modules/merge2": { - "version": "1.4.1", - "resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz", - "integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==", + "node_modules/lodash.isequal": { + "version": "4.5.0", + "resolved": "https://registry.npmjs.org/lodash.isequal/-/lodash.isequal-4.5.0.tgz", + "integrity": "sha512-pDo3lu8Jhfjqls6GkMgpahsF9kCyayhgykjyLMNFTKWrpVdAQtYyB4muAMWozBB4ig/dtWAmsMxLEI8wuz+DYQ==", "dev": true, - "engines": { - "node": ">= 8" - } - }, - "node_modules/micromatch": { - "version": "4.0.5", - "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz", - "integrity": "sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==", - "dev": true, - "dependencies": { - "braces": "^3.0.2", - "picomatch": "^2.3.1" - }, - "engines": { - "node": ">=8.6" - } + "license": "MIT" }, "node_modules/minimatch": { "version": "3.1.2", @@ -940,9 +1171,9 @@ } }, "node_modules/object-inspect": { - "version": "1.13.1", - "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.1.tgz", - "integrity": "sha512-5qoj1RUiKOMsCCNLV1CBiPYE10sziTsnmNxkAI/rZhiD63CF7IqdFGC/XzjWjpSgLf0LxXX3bDFIh0E18f6UhQ==", + "version": "1.13.0", + "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.0.tgz", + "integrity": "sha512-HQ4J+ic8hKrgIt3mqk6cVOVrW2ozL4KdvHlqpBv9vDYWx9ysAgENAdvy4FoGF+KFdhR7nQTNm5J0ctAeOwn+3g==", "dev": true, "funding": { "url": "https://github.com/sponsors/ljharb" @@ -974,13 +1205,13 @@ } }, "node_modules/object.assign": { - "version": "4.1.5", - "resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.5.tgz", - "integrity": "sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ==", + "version": "4.1.4", + "resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.4.tgz", + "integrity": "sha512-1mxKf0e58bvyjSCtKYY4sRe9itRk3PJpquJOjeIkz885CczcI4IvJJDLPS72oowuSh+pBxUFROpX+TU++hxhZQ==", "dev": true, "dependencies": { - "call-bind": "^1.0.5", - "define-properties": "^1.2.1", + "call-bind": "^1.0.2", + "define-properties": "^1.1.4", "has-symbols": "^1.0.3", "object-keys": "^1.1.1" }, @@ -1001,20 +1232,55 @@ } }, "node_modules/openapi-typescript": { - "version": "6.7.4", - "resolved": "https://registry.npmjs.org/openapi-typescript/-/openapi-typescript-6.7.4.tgz", - "integrity": "sha512-EZyeW9Wy7UDCKv0iYmKrq2pVZtquXiD/YHiUClAKqiMi42nodx/EQH11K6fLqjt1IZlJmVokrAsExsBMM2RROQ==", + "version": "7.4.3", + "resolved": "https://registry.npmjs.org/openapi-typescript/-/openapi-typescript-7.4.3.tgz", + "integrity": "sha512-xTIjMIIOv9kNhsr8JxaC00ucbIY/6ZwuJPJBZMSh5FA2dicZN5uM805DWVJojXdom8YI4AQTavPDPHMx/3g0vQ==", "dev": true, + "license": "MIT", "dependencies": { + "@redocly/openapi-core": "^1.25.9", "ansi-colors": "^4.1.3", - "fast-glob": "^3.3.2", - "js-yaml": "^4.1.0", + "change-case": "^5.4.4", + "parse-json": "^8.1.0", "supports-color": "^9.4.0", - "undici": "^5.28.2", "yargs-parser": "^21.1.1" }, "bin": { "openapi-typescript": "bin/cli.js" + }, + "peerDependencies": { + "typescript": "^5.x" + } + }, + "node_modules/openapi-typescript/node_modules/parse-json": { + "version": "8.1.0", + "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-8.1.0.tgz", + "integrity": "sha512-rum1bPifK5SSar35Z6EKZuYPJx85pkNaFrxBK3mwdfSJ1/WKbYrjoW/zTPSjRRamfmVX1ACBIdFAO0VRErW/EA==", + "dev": true, + "license": "MIT", + "dependencies": { + "@babel/code-frame": "^7.22.13", + "index-to-position": "^0.1.2", + "type-fest": "^4.7.1" + }, + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/openapi-typescript/node_modules/type-fest": { + "version": "4.27.0", + "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-4.27.0.tgz", + "integrity": "sha512-3IMSWgP7C5KSQqmo1wjhKrwsvXAtF33jO3QY+Uy++ia7hqvgSK6iXbbg5PbDBc1P2ZbNEDgejOrN4YooXvhwCw==", + "dev": true, + "license": "(MIT OR CC0-1.0)", + "engines": { + "node": ">=16" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" } }, "node_modules/path-is-absolute": { @@ -1026,22 +1292,20 @@ "node": ">=0.10.0" } }, - "node_modules/picomatch": { - "version": "2.3.1", - "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz", - "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==", + "node_modules/pluralize": { + "version": "8.0.0", + "resolved": "https://registry.npmjs.org/pluralize/-/pluralize-8.0.0.tgz", + "integrity": "sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA==", "dev": true, + "license": "MIT", "engines": { - "node": ">=8.6" - }, - "funding": { - "url": "https://github.com/sponsors/jonschlinkert" + "node": ">=4" } }, "node_modules/prettier": { - "version": "3.2.5", - "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.2.5.tgz", - "integrity": "sha512-3/GWa9aOC0YeD7LUfvOG2NiDyhOWRvt1k+rcKhOuYnMY24iiCphgneUfJDyFXd6rZCAnuLBv6UeAULtrhT/F4A==", + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.0.3.tgz", + "integrity": "sha512-L/4pUDMxcNa8R/EthV08Zt42WBO4h1rarVtK0K+QJG0X187OLo7l699jWw0GKuwzkPQ//jMFA/8Xm6Fh3J/DAg==", "dev": true, "bin": { "prettier": "bin/prettier.cjs" @@ -1053,36 +1317,15 @@ "url": "https://github.com/prettier/prettier?sponsor=1" } }, - "node_modules/queue-microtask": { - "version": "1.2.3", - "resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz", - "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/feross" - }, - { - "type": "patreon", - "url": "https://www.patreon.com/feross" - }, - { - "type": "consulting", - "url": "https://feross.org/support" - } - ] - }, "node_modules/regexp.prototype.flags": { - "version": "1.5.2", - "resolved": "https://registry.npmjs.org/regexp.prototype.flags/-/regexp.prototype.flags-1.5.2.tgz", - "integrity": "sha512-NcDiDkTLuPR+++OCKB0nWafEmhg/Da8aUPLPMQbK+bxKKCm1/S5he+AqYa4PlMCVBalb4/yxIRub6qkEx5yJbw==", + "version": "1.5.1", + "resolved": "https://registry.npmjs.org/regexp.prototype.flags/-/regexp.prototype.flags-1.5.1.tgz", + "integrity": "sha512-sy6TXMN+hnP/wMy+ISxg3krXx7BAtWVO4UouuCN/ziM9UEne0euamVNafDfvC83bRNr95y0V5iijeDQFUNpvrg==", "dev": true, "dependencies": { - "call-bind": "^1.0.6", - "define-properties": "^1.2.1", - "es-errors": "^1.3.0", - "set-function-name": "^2.0.1" + "call-bind": "^1.0.2", + "define-properties": "^1.2.0", + "set-function-name": "^2.0.0" }, "engines": { "node": ">= 0.4" @@ -1091,39 +1334,16 @@ "url": "https://github.com/sponsors/ljharb" } }, - "node_modules/reusify": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz", - "integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==", + "node_modules/require-from-string": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz", + "integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==", "dev": true, + "license": "MIT", "engines": { - "iojs": ">=1.0.0", "node": ">=0.10.0" } }, - "node_modules/run-parallel": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz", - "integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/feross" - }, - { - "type": "patreon", - "url": "https://www.patreon.com/feross" - }, - { - "type": "consulting", - "url": "https://feross.org/support" - } - ], - "dependencies": { - "queue-microtask": "^1.2.2" - } - }, "node_modules/semantic-release-plugin-update-version-in-files": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/semantic-release-plugin-update-version-in-files/-/semantic-release-plugin-update-version-in-files-1.1.0.tgz", @@ -1134,23 +1354,6 @@ "glob": "^7.1.3" } }, - "node_modules/set-function-length": { - "version": "1.2.1", - "resolved": "https://registry.npmjs.org/set-function-length/-/set-function-length-1.2.1.tgz", - "integrity": "sha512-j4t6ccc+VsKwYHso+kElc5neZpjtq9EnRICFZtWyBsLojhmeF/ZBd/elqm22WJh/BziDe/SBiOeAt0m2mfLD0g==", - "dev": true, - "dependencies": { - "define-data-property": "^1.1.2", - "es-errors": "^1.3.0", - "function-bind": "^1.1.2", - "get-intrinsic": "^1.2.3", - "gopd": "^1.0.1", - "has-property-descriptors": "^1.0.1" - }, - "engines": { - "node": ">= 0.4" - } - }, "node_modules/set-function-name": { "version": "2.0.1", "resolved": "https://registry.npmjs.org/set-function-name/-/set-function-name-2.0.1.tgz", @@ -1166,18 +1369,14 @@ } }, "node_modules/side-channel": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.0.5.tgz", - "integrity": "sha512-QcgiIWV4WV7qWExbN5llt6frQB/lBven9pqliLXfGPB+K9ZYXxDozp0wLkHS24kWCm+6YXH/f0HhnObZnZOBnQ==", + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.0.4.tgz", + "integrity": "sha512-q5XPytqFEIKHkGdiMIrY10mvLRvnQh42/+GoBlFW3b2LXLE2xxJpZFdm94we0BaoV3RwJyGqg5wS7epxTv0Zvw==", "dev": true, "dependencies": { - "call-bind": "^1.0.6", - "es-errors": "^1.3.0", - "get-intrinsic": "^1.2.4", - "object-inspect": "^1.13.1" - }, - "engines": { - "node": ">= 0.4" + "call-bind": "^1.0.0", + "get-intrinsic": "^1.0.2", + "object-inspect": "^1.9.0" }, "funding": { "url": "https://github.com/sponsors/ljharb" @@ -1207,34 +1406,24 @@ "url": "https://github.com/chalk/supports-color?sponsor=1" } }, - "node_modules/to-regex-range": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz", - "integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==", - "dev": true, - "dependencies": { - "is-number": "^7.0.0" - }, - "engines": { - "node": ">=8.0" - } - }, "node_modules/tr46": { "version": "0.0.3", "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", "integrity": "sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==", "dev": true }, - "node_modules/undici": { - "version": "5.28.4", - "resolved": "https://registry.npmjs.org/undici/-/undici-5.28.4.tgz", - "integrity": "sha512-72RFADWFqKmUb2hmmvNODKL3p9hcB6Gt2DOQMis1SEBaV6a4MH8soBvzg+95CYhCKPFedut2JY9bMfrDl9D23g==", + "node_modules/typescript": { + "version": "5.2.2", + "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.2.2.tgz", + "integrity": "sha512-mI4WrpHsbCIcwT9cF4FZvr80QUeKvsUsUvKDoR+X/7XHQH98xYD8YHZg7ANtz2GtZt/CBq2QJ0thkGJMHfqc1w==", "dev": true, - "dependencies": { - "@fastify/busboy": "^2.0.0" + "peer": true, + "bin": { + "tsc": "bin/tsc", + "tsserver": "bin/tsserver" }, "engines": { - "node": ">=14.0" + "node": ">=14.17" } }, "node_modules/universal-user-agent": { @@ -1244,6 +1433,13 @@ "dev": true, "license": "ISC" }, + "node_modules/uri-js-replace": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/uri-js-replace/-/uri-js-replace-1.0.1.tgz", + "integrity": "sha512-W+C9NWNLFOoBI2QWDp4UT9pv65r2w5Cx+3sTYFvtMdDBxkKt1syCqsUdSFAChbEe1uK5TfS04wt/nGwmaeIQ0g==", + "dev": true, + "license": "MIT" + }, "node_modules/webidl-conversions": { "version": "3.0.1", "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", @@ -1292,16 +1488,16 @@ } }, "node_modules/which-typed-array": { - "version": "1.1.14", - "resolved": "https://registry.npmjs.org/which-typed-array/-/which-typed-array-1.1.14.tgz", - "integrity": "sha512-VnXFiIW8yNn9kIHN88xvZ4yOWchftKDsRJ8fEPacX/wl1lOvBrhsJ/OeJCXq7B0AaijRuqgzSKalJoPk+D8MPg==", + "version": "1.1.11", + "resolved": "https://registry.npmjs.org/which-typed-array/-/which-typed-array-1.1.11.tgz", + "integrity": "sha512-qe9UWWpkeG5yzZ0tNYxDmd7vo58HDBc39mZ0xWWpolAGADdFOzkfamWLDxkOWcvHQKVmdTyQdLD4NOfjLWTKew==", "dev": true, "dependencies": { - "available-typed-arrays": "^1.0.6", - "call-bind": "^1.0.5", + "available-typed-arrays": "^1.0.5", + "call-bind": "^1.0.2", "for-each": "^0.3.3", "gopd": "^1.0.1", - "has-tostringtag": "^1.0.1" + "has-tostringtag": "^1.0.0" }, "engines": { "node": ">= 0.4" @@ -1316,6 +1512,13 @@ "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==", "dev": true }, + "node_modules/yaml-ast-parser": { + "version": "0.0.43", + "resolved": "https://registry.npmjs.org/yaml-ast-parser/-/yaml-ast-parser-0.0.43.tgz", + "integrity": "sha512-2PTINUwsRqSd+s8XxKaJWQlUuEMHJQyEuh2edBbW8KNJz0SJPwUSD2zRWqezFEdN7IzAgeuYHFUCF7o8zRdZ0A==", + "dev": true, + "license": "Apache-2.0" + }, "node_modules/yargs-parser": { "version": "21.1.1", "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz", diff --git a/package.json b/package.json index 1f37a1d..e93875e 100644 --- a/package.json +++ b/package.json @@ -28,7 +28,7 @@ "deep-equal": "^2.0.5", "github-enterprise-server-versions": "^2.0.1", "lodash": "^4.17.21", - "openapi-typescript": "^6.2.1", + "openapi-typescript": "^7.0.0", "prettier": "^3.0.0", "semantic-release-plugin-update-version-in-files": "^1.1.0" }, diff --git a/packages/openapi-webhooks-types-ghec/types.d.ts b/packages/openapi-webhooks-types-ghec/types.d.ts index 75b9c47..fdd8069 100644 --- a/packages/openapi-webhooks-types-ghec/types.d.ts +++ b/packages/openapi-webhooks-types-ghec/types.d.ts @@ -3,2921 +3,6264 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-configuration-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were disabled for a repository. */ post: operations["branch-protection-configuration/disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-configuration-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were enabled for a repository. */ post: operations["branch-protection-configuration/enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-push-ruleset-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass a set of push rules. * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." + * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * - * Note: Delegated bypass for push rules is currently in beta and subject to change. + * Note: Delegated bypass for push rules is currently in beta and subject to change. * @description A push ruleset bypass request was cancelled. */ post: operations["exemption-request-push-ruleset/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-push-ruleset-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass a set of push rules. * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." + * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * - * Note: Delegated bypass for push rules is currently in beta and subject to change. + * Note: Delegated bypass for push rules is currently in beta and subject to change. * @description A push ruleset bypass request was completed. */ post: operations["exemption-request-push-ruleset/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-push-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass a set of push rules. * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." + * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * - * Note: Delegated bypass for push rules is currently in beta and subject to change. + * Note: Delegated bypass for push rules is currently in beta and subject to change. * @description A push ruleset bypass request was created. */ post: operations["exemption-request-push-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-push-ruleset-response-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass a set of push rules. * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." + * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * - * Note: Delegated bypass for push rules is currently in beta and subject to change. + * Note: Delegated bypass for push rules is currently in beta and subject to change. * @description A push ruleset bypass response was dismissed. */ post: operations["exemption-request-push-ruleset/response-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-push-ruleset-response-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass a set of push rules. * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." + * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * - * Note: Delegated bypass for push rules is currently in beta and subject to change. + * Note: Delegated bypass for push rules is currently in beta and subject to change. * @description A response either approving or rejecting the push ruleset bypass request was submitted. */ post: operations["exemption-request-push-ruleset/response-submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning push protection bypass request was cancelled. */ post: operations["exemption-request-secret-scanning/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning bypass request was completed. */ post: operations["exemption-request-secret-scanning/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning push protection bypass request was created. */ post: operations["exemption-request-secret-scanning/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-response-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning push protection bypass response was dismissed. */ post: operations["exemption-request-secret-scanning/response-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-response-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A response either approving or rejecting the secret scanning push protection bypass request was submitted. */ post: operations["exemption-request-secret-scanning/response-submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-cloud@latest//developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-cloud@latest//graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-cloud@latest//graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-cloud@latest//rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a custom property. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description A new custom property was created. */ post: operations["custom-property/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a custom property. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description A custom property was deleted. */ post: operations["custom-property/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a custom property. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description A custom property was updated. */ post: operations["custom-property/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-values-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to custom property values for a repository. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties for a repository, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/repos/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties for a repository, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/repos/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description The custom property values of a repository were updated. */ post: operations["custom-property-values/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. */ post: operations["dependabot-alert/auto-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. */ post: operations["dependabot-alert/auto-reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-cloud@latest//developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-cloud@latest//rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-cloud@latest//developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-cloud@latest//rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-cloud@latest//actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-cloud@latest//get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-cloud@latest//rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-cloud@latest//get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-cloud@latest//rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-cloud@latest//apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-cloud@latest//apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-cloud@latest//communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-cloud@latest//communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-cloud@latest//rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-cloud@latest//rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-cloud@latest//rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-cloud@latest//rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-cloud@latest//rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-cloud@latest//rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. * @description Someone cancelled a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. */ post: operations["marketplace-purchase/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. * @description Someone upgraded or downgraded a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. */ post: operations["marketplace-purchase/changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-pending-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. * @description Someone downgraded or cancelled a GitHub Marketplace plan. The new plan or cancellation will take effect at the end of the current billing cycle. When the change takes effect, the `changed` or `cancelled` event will be sent. */ post: operations["marketplace-purchase/pending-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-pending-change-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. * @description Someone cancelled a pending change to a GitHub Marketplace plan. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle. */ post: operations["marketplace-purchase/pending-change-cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-purchased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. * @description Someone purchased a GitHub Marketplace plan. The change will take effect on the account immediately. */ post: operations["marketplace-purchase/purchased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-cloud@latest//rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-cloud@latest//rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-cloud@latest//rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-cloud@latest//rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-cloud@latest//rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "merge-group-checks-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. * @description Status checks were requested for a merge group. This happens when a merge group is created or added to by the merge queue because a pull request was queued. * - * When you receive this event, you should perform checks on the head SHA and report status back using check runs or commit statuses. + * When you receive this event, you should perform checks on the head SHA and report status back using check runs or commit statuses. */ post: operations["merge-group/checks-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "merge-group-destroyed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. * @description The merge queue groups pull requests together to be merged. This event indicates that one of those merge groups was destroyed. This happens when a pull request is removed from the queue: any group containing that pull request is also destroyed. * - * When you receive this event, you may want to cancel any checks that are running on the head SHA to avoid wasting computing resources on a merge group that will not be used. + * When you receive this event, you may want to cancel any checks that are running on the head SHA to avoid wasting computing resources on a merge group that will not be used. */ post: operations["merge-group/destroyed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "org-block-blocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/enterprise-cloud@latest//communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/enterprise-cloud@latest//rest/orgs/blocking)" in the REST API documentation. * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. + * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. * @description A user was blocked from the organization. */ post: operations["org-block/blocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "org-block-unblocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/enterprise-cloud@latest//communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/enterprise-cloud@latest//rest/orgs/blocking)" in the REST API documentation. * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. + * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. * @description A previously blocked user was unblocked from the organization. */ post: operations["org-block/unblocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-cloud@latest//pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-cloud@latest//rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-cloud@latest//pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-cloud@latest//rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-status-update-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." * - * For activity relating to a project, use the `projects_v2` event. + * For activity relating to a project, use the `projects_v2` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A status update was added to a project in the organization. */ post: operations["projects-v2-status-update/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-status-update-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." * - * For activity relating to a project, use the `projects_v2` event. + * For activity relating to a project, use the `projects_v2` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A status update was removed from a project in the organization. */ post: operations["projects-v2-status-update/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-status-update-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." * - * For activity relating to a project, use the `projects_v2` event. + * For activity relating to a project, use the `projects_v2` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A status update was edited on a project in the organization. */ post: operations["projects-v2-status-update/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-dequeued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from the merge queue. */ post: operations["pull-request/dequeued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-enqueued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to the merge queue. */ post: operations["pull-request/enqueued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-cloud@latest//rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-cloud@latest//rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-cloud@latest//rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/enterprise-cloud@latest//code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. * @description A repository security advisory was published. */ post: operations["repository-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-advisory-reported": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/enterprise-cloud@latest//code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. * @description A private vulnerability report was submitted. */ post: operations["repository-advisory/reported"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-cloud@latest//rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-cloud@latest//rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-import": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a repository is imported to GitHub Enterprise Cloud. For more information, see "[Importing a repository with GitHub Importer](https://docs.github.com/enterprise-cloud@latest//get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." For more information about the API to manage imports, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/migrations/source-imports). */ post: operations["repository-import"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was created. */ post: operations["repository-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was deleted. */ post: operations["repository-ruleset/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was edited. */ post: operations["repository-ruleset/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-validated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was validated. */ post: operations["secret-scanning-alert/validated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-cloud@latest//code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-cloud@latest//code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-cloud@latest//code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-cloud@latest//code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-cloud@latest//code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-cloud@latest//get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-cloud@latest//rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-cloud@latest//get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-cloud@latest//rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-cloud@latest//rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-cloud@latest//rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-parent-issue-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A parent issue was added to an issue. */ post: operations["sub-issues/parent-issue-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-parent-issue-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A parent issue was removed from an issue. */ post: operations["sub-issues/parent-issue-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-sub-issue-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A sub-issue was added to an issue. */ post: operations["sub-issues/sub-issue-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-sub-issue-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A sub-issue was removed from an issue. */ post: operations["sub-issues/sub-issue-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-cloud@latest//account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-cloud@latest//rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-cloud@latest//actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-cloud@latest//actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-cloud@latest//actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-cloud@latest//actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-cloud@latest//actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection configuration disabled event */ @@ -2933,8 +6276,8 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/enterprise-cloud@latest//admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/enterprise-cloud@latest//admin/overview/about-enterprise-accounts)." */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2963,8 +6306,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-cloud@latest//apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-cloud@latest//apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2975,7 +6318,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2997,7 +6340,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -3266,34 +6609,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3331,34 +6674,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3655,10 +6998,8 @@ export interface components { /** @description The comment the requester provided when creating the exemption request. */ requester_comment?: string | null; /** @description Metadata about the exemption request. */ - metadata?: - | components["schemas"]["exemption-request-secret-scanning-metadata"] - | Record - | null; + metadata?: (Record | null) & + components["schemas"]["exemption-request-secret-scanning-metadata"]; /** * Format: date-time * @description The date and time the exemption request will expire. @@ -3886,9 +7227,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3896,7 +7237,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5955,13 +9297,11 @@ export interface components { /** @description Whether the property is required. */ required?: boolean; /** @description Default value of the property */ - default_value?: string | string[] | null | unknown[]; + default_value?: (null | unknown[]) & (string | string[]); /** @description Short description of the property */ description?: string | null; - /** - * @description An ordered list of the allowed values of the property. - * The property can have up to 200 allowed values. - */ + /** @description An ordered list of the allowed values of the property. + * The property can have up to 200 allowed values. */ allowed_values?: string[] | null; /** * @description Who can edit the values of the property @@ -6014,7 +9354,7 @@ export interface components { /** @description The name of the property */ property_name: string; /** @description The value assigned to the property */ - value: string | string[] | null | unknown[]; + value: (null | unknown[]) & (string | string[]); }; /** delete event */ "webhook-delete": { @@ -6049,10 +9389,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -6086,16 +9426,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -6105,7 +9445,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -6119,14 +9459,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -6136,7 +9476,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -6160,8 +9500,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -6179,37 +9519,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert auto-reopened event */ "webhook-dependabot-alert-auto-reopened": { /** @enum {string} */ @@ -6921,14 +10261,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -8702,7 +12039,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -9641,8 +12979,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -10246,7 +13584,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -10440,11 +13778,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -10507,11 +13849,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -17597,7 +20939,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19764,7 +23106,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20614,12 +23956,10 @@ export interface components { /** @enum {string} */ action: "added"; changes?: { - /** - * @description This field is included for legacy purposes; use the `role_name` field instead. The `maintain` - * role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role - * assigned to the collaborator, use the `role_name` field instead, which will provide the full - * role name, including custom roles. - */ + /** @description This field is included for legacy purposes; use the `role_name` field instead. The `maintain` + * role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role + * assigned to the collaborator, use the `role_name` field instead, which will provide the full + * role name, including custom roles. */ permission?: { /** @enum {string} */ to: "write" | "admin" | "read"; @@ -20851,6 +24191,7 @@ export interface components { /** * Merge Group * @description A group of pull requests that the merge queue has grouped together to be merged. + * */ "merge-group": { /** @description The SHA of the merge group. */ @@ -21622,19 +24963,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -22817,42 +26155,37 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes altered values for text, number, date, single select, and iteration fields, along with the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes altered values for text, number, date, single select, and iteration fields, along with the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; field_name?: string; project_number?: number; - from?: - | string - | number - | components["schemas"]["projects-v2-single-select-option"] - | components["schemas"]["projects-v2-iteration-setting"] - | null - | Record; - to?: - | string - | number - | components["schemas"]["projects-v2-single-select-option"] - | components["schemas"]["projects-v2-iteration-setting"] - | null - | Record; + from?: (null | Record) & + ( + | string + | number + | components["schemas"]["projects-v2-single-select-option"] + | components["schemas"]["projects-v2-iteration-setting"] + ); + to?: (null | Record) & + ( + | string + | number + | components["schemas"]["projects-v2-single-select-option"] + | components["schemas"]["projects-v2-iteration-setting"] + ); }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -23363,17 +26696,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23440,7 +26773,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23448,9 +26781,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23460,8 +26793,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23710,17 +27043,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23787,7 +27120,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23795,9 +27128,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23807,8 +27140,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24031,9 +27364,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24068,8 +27400,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24119,9 +27451,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -24586,17 +27917,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24663,7 +27994,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24671,9 +28002,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24683,8 +28014,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24933,17 +28264,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25010,7 +28341,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25018,9 +28349,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25030,8 +28361,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25254,9 +28585,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -25291,8 +28621,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -25342,9 +28672,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25808,17 +29137,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25885,7 +29214,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25893,9 +29222,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25905,8 +29234,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26152,17 +29481,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26229,7 +29558,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26237,9 +29566,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -26249,8 +29578,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26473,9 +29802,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26510,8 +29838,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -26561,9 +29889,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -26703,31 +30030,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27104,17 +30431,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27181,7 +30508,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27189,17 +30516,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27448,17 +30775,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27525,7 +30852,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27533,17 +30860,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27766,9 +31093,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27803,8 +31129,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -27854,9 +31180,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28316,17 +31641,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28393,7 +31718,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28401,9 +31726,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28413,8 +31738,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28663,17 +31988,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28740,7 +32065,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28748,9 +32073,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28760,8 +32085,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28984,9 +32309,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29021,8 +32345,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -29072,9 +32396,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29569,17 +32892,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29646,7 +32969,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29654,9 +32977,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29666,8 +32989,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29916,17 +33239,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29993,7 +33316,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30001,9 +33324,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30013,8 +33336,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30237,9 +33560,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30274,8 +33596,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -30325,9 +33647,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -30791,17 +34112,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30868,7 +34189,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30876,9 +34197,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30888,8 +34209,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31138,17 +34459,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31215,7 +34536,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31223,9 +34544,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31235,8 +34556,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31459,9 +34780,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31496,8 +34816,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -31547,9 +34867,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32012,17 +35331,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32089,7 +35408,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32097,9 +35416,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32109,8 +35428,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32359,17 +35678,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32436,7 +35755,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32444,9 +35763,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32456,8 +35775,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32680,9 +35999,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -32717,8 +36035,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -32768,9 +36086,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33432,17 +36749,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33509,7 +36826,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33517,9 +36834,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33529,8 +36846,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33772,17 +37089,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33849,7 +37166,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33857,9 +37174,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33869,8 +37186,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34048,9 +37365,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34085,8 +37401,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -34136,9 +37452,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34593,17 +37908,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -34670,7 +37985,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -34678,9 +37993,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -34690,8 +38005,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34933,17 +38248,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35010,7 +38325,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35018,9 +38333,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -35030,8 +38345,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -35209,9 +38524,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35246,8 +38560,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -35297,9 +38611,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35909,17 +39222,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35986,7 +39299,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35994,9 +39307,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36006,8 +39319,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36249,17 +39562,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36326,7 +39639,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36334,9 +39647,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36346,8 +39659,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36525,9 +39838,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36562,8 +39874,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -36613,9 +39925,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -37070,17 +40381,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37147,7 +40458,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37155,9 +40466,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37167,8 +40478,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37410,17 +40721,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37487,7 +40798,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37495,9 +40806,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37507,8 +40818,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37686,9 +40997,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -37723,8 +41033,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37774,9 +41084,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38374,7 +41683,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38665,7 +41974,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38837,9 +42146,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -38874,8 +42182,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -38925,9 +42233,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39116,9 +42423,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -39469,17 +42775,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39546,7 +42852,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39809,17 +43115,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39886,7 +43192,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39894,9 +43200,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39906,8 +43212,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40130,9 +43436,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40167,8 +43472,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -40218,9 +43523,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40368,8 +43672,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -40720,17 +44024,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40797,7 +44101,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40805,9 +44109,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40817,8 +44121,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41067,17 +44371,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41144,7 +44448,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41152,9 +44456,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41164,8 +44468,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41388,9 +44692,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -41425,8 +44728,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -41476,9 +44779,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -41644,13 +44946,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -42001,17 +45300,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -42078,7 +45377,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42086,9 +45385,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -42098,8 +45397,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -42348,17 +45647,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -42425,7 +45724,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42433,9 +45732,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -42445,8 +45744,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -42669,9 +45968,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42706,8 +46004,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42757,9 +46055,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42907,8 +46204,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -43259,17 +46556,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -43336,7 +46633,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43344,9 +46641,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -43356,8 +46653,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -43606,17 +46903,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -43683,7 +46980,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43691,9 +46988,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -43703,8 +47000,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -43927,9 +47224,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43964,8 +47260,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -44015,9 +47311,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44183,9 +47478,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -44535,17 +47828,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44612,7 +47905,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44620,9 +47913,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44632,8 +47925,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -44875,17 +48168,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44952,7 +48245,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44960,9 +48253,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44972,8 +48265,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45151,9 +48444,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45188,8 +48480,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45239,9 +48531,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45757,7 +49048,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46055,7 +49346,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46229,9 +49520,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46266,8 +49556,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46317,9 +49607,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -46987,7 +50276,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47285,7 +50574,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47459,9 +50748,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -47496,8 +50784,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -47547,9 +50835,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48161,17 +51448,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48238,7 +51525,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48246,9 +51533,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48258,8 +51545,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48578,7 +51865,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48586,9 +51873,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48598,8 +51885,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48822,9 +52109,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -48859,8 +52145,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -48910,9 +52196,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49376,17 +52661,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -49453,7 +52738,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49461,9 +52746,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -49473,8 +52758,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -49723,17 +53008,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -49800,7 +53085,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49808,9 +53093,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -49820,8 +53105,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -50044,9 +53329,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -50081,8 +53365,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -50132,9 +53416,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -50598,17 +53881,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -50675,7 +53958,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -50683,9 +53966,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -50695,8 +53978,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -51015,7 +54298,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -51023,9 +54306,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -51035,8 +54318,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -51259,9 +54542,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -51296,8 +54578,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -51347,9 +54629,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -51812,17 +55093,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -51889,7 +55170,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -51897,9 +55178,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -51909,8 +55190,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -52159,17 +55440,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -52236,7 +55517,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52244,9 +55525,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -52256,8 +55537,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -52480,9 +55761,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -52517,8 +55797,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -52568,9 +55848,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -53030,7 +56309,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53153,19 +56432,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -53178,7 +56461,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -53190,21 +56474,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -53955,19 +57237,19 @@ export interface components { /** @description A repository security advisory. */ "repository-advisory": { /** @description The GitHub Security Advisory ID. */ - ghsa_id: string; + readonly ghsa_id: string; /** @description The Common Vulnerabilities and Exposures (CVE) ID. */ cve_id: string | null; /** * Format: uri * @description The API URL for the advisory. */ - url: string; + readonly url: string; /** * Format: uri * @description The URL for the advisory. */ - html_url: string; + readonly html_url: string; /** @description A short summary of the advisory. */ summary: string; /** @description A detailed description of what the advisory entails. */ @@ -53978,10 +57260,10 @@ export interface components { */ severity: "critical" | "high" | "medium" | "low" | null; /** @description The author of the advisory. */ - author: null; + readonly author: null & components["schemas"]["simple-user"]; /** @description The publisher of the advisory. */ - publisher: null; - identifiers: readonly { + readonly publisher: null & components["schemas"]["simple-user"]; + readonly identifiers: { /** * @description The type of identifier. * @enum {string} @@ -53999,28 +57281,28 @@ export interface components { * Format: date-time * @description The date and time of when the advisory was created, in ISO 8601 format. */ - created_at: string | null; + readonly created_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was last updated, in ISO 8601 format. */ - updated_at: string | null; + readonly updated_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was published, in ISO 8601 format. */ - published_at: string | null; + readonly published_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was closed, in ISO 8601 format. */ - closed_at: string | null; + readonly closed_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was withdrawn, in ISO 8601 format. */ - withdrawn_at: string | null; - submission: { + readonly withdrawn_at: string | null; + readonly submission: { /** @description Whether a private vulnerability report was accepted by the repository's administrators. */ readonly accepted: boolean; } | null; @@ -54031,14 +57313,14 @@ export interface components { /** @description The CVSS vector. */ vector_string: string | null; /** @description The CVSS score. */ - score: number | null; + readonly score: number | null; } | null; - cwes: - | readonly { + readonly cwes: + | { /** @description The Common Weakness Enumeration (CWE) identifier. */ cwe_id: string; /** @description The name of the CWE. */ - name: string; + readonly name: string; }[] | null; /** @description A list of only the CWE IDs. */ @@ -54050,15 +57332,15 @@ export interface components { type?: components["schemas"]["security-advisory-credit-types"]; }[] | null; - credits_detailed: - | readonly components["schemas"]["repository-advisory-credit"][] + readonly credits_detailed: + | components["schemas"]["repository-advisory-credit"][] | null; /** @description A list of users that collaborate on the advisory. */ collaborating_users: components["schemas"]["simple-user"][] | null; /** @description A list of teams that collaborate on the advisory. */ collaborating_teams: components["schemas"]["team"][] | null; /** @description A temporary private fork of the advisory's repository for collaborating on a fix. */ - private_fork: null; + readonly private_fork: null & components["schemas"]["simple-repository"]; }; /** @description A product affected by the vulnerability detailed in a repository security advisory. */ "repository-advisory-vulnerability": { @@ -54442,8 +57724,8 @@ export interface components { /** * @description The target of the ruleset * - * > [!NOTE] - * > The `push` target is in beta and is subject to change. + * > [!NOTE] + * > The `push` target is in beta and is subject to change. * @enum {string} */ target?: "branch" | "tag" | "push"; @@ -54459,7 +57741,7 @@ export interface components { bypass_actors?: components["schemas"]["repository-ruleset-bypass-actor"][]; /** * @description The bypass type of the user making the API request for this ruleset. This field is only returned when - * querying the repository-level endpoint. + * querying the repository-level endpoint. * @enum {string} */ current_user_can_bypass?: "always" | "pull_requests_only" | "never"; @@ -54475,11 +57757,15 @@ export interface components { }; }; conditions?: - | null | ( - | components["schemas"]["repository-ruleset-conditions"] - | components["schemas"]["org-ruleset-conditions"] - ); + | null + | ( + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"] + ) + ) + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"]; rules?: components["schemas"]["repository-rule"][]; /** Format: date-time */ created_at?: string; @@ -54496,7 +57782,8 @@ export interface components { * @description An actor that can bypass rules in a ruleset */ "repository-ruleset-bypass-actor": { - /** @description The ID of the actor that can bypass a ruleset. If `actor_type` is `OrganizationAdmin`, this should be `1`. If `actor_type` is `DeployKey`, this should be null. `OrganizationAdmin` is not applicable for personal repositories. */ + /** @description The ID of the actor that can bypass a ruleset. If `actor_type` is `OrganizationAdmin`, this should be `1`. If `actor_type` is `DeployKey`, this should be null. `OrganizationAdmin` is not applicable for personal repositories. + * */ actor_id?: number | null; /** * @description The type of actor that can bypass a ruleset. @@ -54532,6 +57819,7 @@ export interface components { /** * Organization ruleset conditions * @description Conditions for an organization ruleset. The conditions object should contain both `repository_name` and `ref_name` properties or both `repository_id` and `ref_name` properties. + * */ "org-ruleset-conditions": | (components["schemas"]["repository-ruleset-conditions"] & @@ -55373,10 +58661,8 @@ export interface components { resolution_comment?: string | null; /** @description The type of secret that secret scanning detected. */ secret_type?: string; - /** - * @description User-friendly name for the detected secret, matching the `secret_type`. - * For a list of built-in patterns, see "[Supported secret scanning patterns](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." - */ + /** @description User-friendly name for the detected secret, matching the `secret_type`. + * For a list of built-in patterns, see "[Supported secret scanning patterns](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." */ secret_type_display_name?: string; /** * @description The token status as of the latest validity check. @@ -55853,34 +59139,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -56096,34 +59382,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -56633,10 +59919,9 @@ export interface components { body?: string | null; user: null | components["schemas"]["simple-user"]; /** @description Labels to associate with this issue; pass one or more label names to replace the set of labels on this issue; send an empty array to clear all labels from the issue; note that the labels are silently dropped for users without push access to the repository */ - labels: OneOf< - [ - string, - { + labels: ( + | string + | { /** Format: int64 */ id?: number; node_id?: string; @@ -56646,9 +59931,8 @@ export interface components { description?: string | null; color?: string | null; default?: boolean; - }, - ] - >[]; + } + )[]; assignee: null | components["schemas"]["simple-user"]; assignees?: components["schemas"]["simple-user"][] | null; milestone: null | components["schemas"]["milestone"]; @@ -57037,7 +60321,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -57289,7 +60573,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -57541,7 +60825,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -57824,7 +61108,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -58076,7 +61360,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -59858,22 +63142,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were disabled for a repository. - */ "branch-protection-configuration/disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59890,6 +63163,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59899,20 +63174,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were enabled for a repository. - */ "branch-protection-configuration/enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59929,6 +63200,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59938,18 +63211,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59966,6 +63237,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59975,18 +63248,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60003,6 +63274,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60012,18 +63285,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-cloud@latest//rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60040,6 +63311,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60049,22 +63322,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass a set of push rules. - * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * - * Note: Delegated bypass for push rules is currently in beta and subject to change. - * @description A push ruleset bypass request was cancelled. - */ "exemption-request-push-ruleset/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60081,6 +63348,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60090,22 +63359,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass a set of push rules. - * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * - * Note: Delegated bypass for push rules is currently in beta and subject to change. - * @description A push ruleset bypass request was completed. - */ "exemption-request-push-ruleset/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60122,6 +63385,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60131,22 +63396,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass a set of push rules. - * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * - * Note: Delegated bypass for push rules is currently in beta and subject to change. - * @description A push ruleset bypass request was created. - */ "exemption-request-push-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60163,6 +63422,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60172,22 +63433,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass a set of push rules. - * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * - * Note: Delegated bypass for push rules is currently in beta and subject to change. - * @description A push ruleset bypass response was dismissed. - */ "exemption-request-push-ruleset/response-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60204,6 +63459,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60213,22 +63470,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass a set of push rules. - * - * For more information, see "[Managing requests to bypass push rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository#managing-requests-to-bypass-push-rules)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * - * Note: Delegated bypass for push rules is currently in beta and subject to change. - * @description A response either approving or rejecting the push ruleset bypass request was submitted. - */ "exemption-request-push-ruleset/response-submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60245,6 +63496,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60254,22 +63507,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning push protection bypass request was cancelled. - */ "exemption-request-secret-scanning/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60286,6 +63533,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60295,22 +63544,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning bypass request was completed. - */ "exemption-request-secret-scanning/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60327,6 +63570,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60336,22 +63581,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning push protection bypass request was created. - */ "exemption-request-secret-scanning/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60368,6 +63607,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60377,22 +63618,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning push protection bypass response was dismissed. - */ "exemption-request-secret-scanning/response-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60409,6 +63644,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60418,22 +63655,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A response either approving or rejecting the secret scanning push protection bypass request was submitted. - */ "exemption-request-secret-scanning/response-submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60450,6 +63681,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60459,25 +63692,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60494,6 +63718,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60503,25 +63729,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60538,6 +63755,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60547,25 +63766,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-cloud@latest//developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60582,6 +63792,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60591,25 +63803,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60626,6 +63829,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60635,25 +63840,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60670,6 +63866,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60679,25 +63877,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-cloud@latest//graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-cloud@latest//rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60714,6 +63903,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60723,25 +63914,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-cloud@latest//rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-cloud@latest//graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-cloud@latest//rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60758,6 +63940,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60767,18 +63951,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60795,6 +63977,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60804,18 +63988,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60832,6 +64014,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60841,18 +64025,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60869,6 +64051,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60878,18 +64062,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60906,6 +64088,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60915,18 +64099,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60943,6 +64125,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60952,18 +64136,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-cloud@latest//code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-cloud@latest//rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60980,6 +64162,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60989,20 +64173,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-cloud@latest//rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61019,6 +64199,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61028,21 +64210,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61059,6 +64236,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61068,20 +64247,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a custom property. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description A new custom property was created. - */ "custom-property/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61098,6 +64273,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61107,20 +64284,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a custom property. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description A custom property was deleted. - */ "custom-property/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61137,6 +64310,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61146,20 +64321,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a custom property. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/orgs/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description A custom property was updated. - */ "custom-property/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61176,6 +64347,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61185,20 +64358,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to custom property values for a repository. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties for a repository, see "[Custom properties](https://docs.github.com/enterprise-cloud@latest//rest/repos/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description The custom property values of a repository were updated. - */ "custom-property-values/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61215,6 +64384,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61224,21 +64395,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61255,6 +64421,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61264,23 +64432,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. - */ "dependabot-alert/auto-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61297,6 +64458,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61306,23 +64469,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. - */ "dependabot-alert/auto-reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61339,6 +64495,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61348,23 +64506,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61381,6 +64532,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61390,23 +64543,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61423,6 +64569,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61432,23 +64580,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61465,6 +64606,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61474,23 +64617,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61507,6 +64643,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61516,23 +64654,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61549,6 +64680,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61558,18 +64691,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-cloud@latest//developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-cloud@latest//rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61586,6 +64717,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61595,18 +64728,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-cloud@latest//developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-cloud@latest//rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61623,6 +64754,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61632,20 +64765,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61662,6 +64791,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61671,18 +64802,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-cloud@latest//actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61699,6 +64828,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61708,20 +64839,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61738,6 +64865,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61747,20 +64876,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61777,6 +64902,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61786,20 +64913,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61816,6 +64939,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61825,23 +64950,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-cloud@latest//actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-cloud@latest//rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61858,6 +64976,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61867,23 +64987,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61900,6 +65013,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61909,23 +65024,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61942,6 +65050,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61951,23 +65061,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61984,6 +65087,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61993,23 +65098,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62026,6 +65124,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62035,23 +65135,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62068,6 +65161,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62077,23 +65172,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62110,6 +65198,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62119,23 +65209,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62152,6 +65235,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62161,23 +65246,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62194,6 +65272,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62203,23 +65283,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62236,6 +65309,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62245,23 +65320,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62278,6 +65346,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62287,23 +65357,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62320,6 +65383,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62329,23 +65394,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62362,6 +65420,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62371,23 +65431,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62404,6 +65457,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62413,23 +65468,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62446,6 +65494,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62455,23 +65505,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62488,6 +65531,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62497,23 +65542,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62530,6 +65568,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62539,23 +65579,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62572,6 +65605,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62581,23 +65616,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-cloud@latest//discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62614,6 +65642,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62623,17 +65653,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-cloud@latest//get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-cloud@latest//rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62650,6 +65679,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62659,20 +65690,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-cloud@latest//apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62689,6 +65716,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62698,17 +65727,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-cloud@latest//communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62725,6 +65753,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62734,18 +65764,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62762,6 +65790,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62771,18 +65801,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62799,6 +65827,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62808,18 +65838,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62836,6 +65864,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62845,18 +65875,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62873,6 +65901,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62882,18 +65912,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62910,6 +65938,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62919,18 +65949,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62947,6 +65975,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62956,16 +65986,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62982,6 +66012,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62991,18 +66023,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-cloud@latest//developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-cloud@latest//rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63019,6 +66049,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63028,20 +66060,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-cloud@latest//rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63058,6 +66086,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63067,20 +66097,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-cloud@latest//rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63097,6 +66123,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63106,20 +66134,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-cloud@latest//rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-cloud@latest//rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63136,6 +66160,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63145,20 +66171,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63175,6 +66197,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63184,20 +66208,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63214,6 +66234,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63223,20 +66245,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63253,6 +66271,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63262,20 +66282,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63292,6 +66308,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63301,20 +66319,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63331,6 +66345,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63340,20 +66356,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63370,6 +66382,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63379,20 +66393,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63409,6 +66419,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63418,20 +66430,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63448,6 +66456,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63457,20 +66467,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63487,6 +66493,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63496,20 +66504,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63526,6 +66530,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63535,20 +66541,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63565,6 +66567,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63574,20 +66578,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63604,6 +66604,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63613,20 +66615,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63643,6 +66641,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63652,20 +66652,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63682,6 +66678,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63691,20 +66689,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63721,6 +66715,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63730,20 +66726,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-cloud@latest//rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-cloud@latest//issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63760,6 +66752,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63769,20 +66763,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-cloud@latest//rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63799,6 +66789,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63808,20 +66800,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-cloud@latest//rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63838,6 +66826,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63847,20 +66837,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-cloud@latest//rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63877,6 +66863,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63886,16 +66874,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. - * @description Someone cancelled a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. - */ "marketplace-purchase/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63912,6 +66900,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63921,16 +66911,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. - * @description Someone upgraded or downgraded a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. - */ "marketplace-purchase/changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63947,6 +66937,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63956,16 +66948,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. - * @description Someone downgraded or cancelled a GitHub Marketplace plan. The new plan or cancellation will take effect at the end of the current billing cycle. When the change takes effect, the `changed` or `cancelled` event will be sent. - */ "marketplace-purchase/pending-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63982,6 +66974,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63991,16 +66985,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. - * @description Someone cancelled a pending change to a GitHub Marketplace plan. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle. - */ "marketplace-purchase/pending-change-cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64017,6 +67011,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64026,16 +67022,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/enterprise-cloud@latest//rest/apps/marketplace)" in the REST API documentation. - * @description Someone purchased a GitHub Marketplace plan. The change will take effect on the account immediately. - */ "marketplace-purchase/purchased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64052,6 +67048,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64061,18 +67059,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-cloud@latest//rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64089,6 +67085,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64098,18 +67096,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-cloud@latest//rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64126,6 +67122,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64135,18 +67133,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-cloud@latest//organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-cloud@latest//rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64163,6 +67159,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64172,18 +67170,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-cloud@latest//rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64200,6 +67196,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64209,18 +67207,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-cloud@latest//rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64237,6 +67233,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64246,20 +67244,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. - * @description Status checks were requested for a merge group. This happens when a merge group is created or added to by the merge queue because a pull request was queued. - * - * When you receive this event, you should perform checks on the head SHA and report status back using check runs or commit statuses. - */ "merge-group/checks-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64276,6 +67270,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64285,20 +67281,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. - * @description The merge queue groups pull requests together to be merged. This event indicates that one of those merge groups was destroyed. This happens when a pull request is removed from the queue: any group containing that pull request is also destroyed. - * - * When you receive this event, you may want to cancel any checks that are running on the head SHA to avoid wasting computing resources on a merge group that will not be used. - */ "merge-group/destroyed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64315,6 +67307,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64324,18 +67318,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64352,6 +67344,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64361,20 +67355,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64391,6 +67381,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64400,20 +67392,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64430,6 +67418,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64439,20 +67429,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64469,6 +67455,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64478,20 +67466,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64508,6 +67492,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64517,20 +67503,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-cloud@latest//issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-cloud@latest//rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64547,6 +67529,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64556,20 +67540,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/enterprise-cloud@latest//communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/enterprise-cloud@latest//rest/orgs/blocking)" in the REST API documentation. - * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. - * @description A user was blocked from the organization. - */ "org-block/blocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64586,6 +67566,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64595,20 +67577,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/enterprise-cloud@latest//communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/enterprise-cloud@latest//rest/orgs/blocking)" in the REST API documentation. - * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. - * @description A previously blocked user was unblocked from the organization. - */ "org-block/unblocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64625,6 +67603,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64634,20 +67614,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64664,6 +67640,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64673,20 +67651,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64703,6 +67677,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64712,20 +67688,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64742,6 +67714,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64751,20 +67725,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64781,6 +67751,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64790,20 +67762,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-cloud@latest//organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-cloud@latest//rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64820,6 +67788,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64829,18 +67799,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64857,6 +67825,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64866,18 +67836,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64894,6 +67862,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64903,17 +67873,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-cloud@latest//pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-cloud@latest//rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64930,6 +67899,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64939,21 +67910,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64970,6 +67936,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64979,21 +67947,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65010,6 +67973,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65019,21 +67984,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65050,6 +68010,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65059,21 +68021,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-cloud@latest//authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65090,6 +68047,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65099,13 +68058,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65122,6 +68084,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65131,22 +68095,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65163,6 +68121,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65172,22 +68132,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65204,6 +68158,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65213,22 +68169,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65245,6 +68195,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65254,22 +68206,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65286,6 +68232,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65295,22 +68243,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65327,6 +68269,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65336,22 +68280,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65368,6 +68306,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65377,22 +68317,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65409,6 +68343,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65418,22 +68354,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65450,6 +68380,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65459,22 +68391,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65491,6 +68417,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65500,22 +68428,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65532,6 +68454,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65541,22 +68465,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65573,6 +68491,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65582,22 +68502,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65614,6 +68528,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65623,22 +68539,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65655,6 +68565,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65664,22 +68576,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-cloud@latest//issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-cloud@latest//rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65696,6 +68602,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65705,23 +68613,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65738,6 +68639,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65747,23 +68650,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65780,6 +68676,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65789,23 +68687,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65822,6 +68713,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65831,23 +68724,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65864,6 +68750,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65873,23 +68761,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65906,6 +68787,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65915,23 +68798,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65948,6 +68824,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65957,23 +68835,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65990,6 +68861,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65999,23 +68872,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66032,6 +68898,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66041,23 +68909,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66074,6 +68935,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66083,23 +68946,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66116,6 +68972,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66125,23 +68983,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66158,6 +69009,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66167,23 +69020,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66200,6 +69046,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66209,23 +69057,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." - * - * For activity relating to a project, use the `projects_v2` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A status update was added to a project in the organization. - */ "projects-v2-status-update/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66242,6 +69083,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66251,23 +69094,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." - * - * For activity relating to a project, use the `projects_v2` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A status update was removed from a project in the organization. - */ "projects-v2-status-update/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66284,6 +69120,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66293,23 +69131,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-cloud@latest//issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." - * - * For activity relating to a project, use the `projects_v2` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A status update was edited on a project in the organization. - */ "projects-v2-status-update/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66326,6 +69157,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66335,17 +69168,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66362,6 +69194,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66371,20 +69205,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66401,6 +69231,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66410,20 +69242,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66440,6 +69268,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66449,20 +69279,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66479,6 +69305,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66488,20 +69316,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66518,6 +69342,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66527,20 +69353,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66557,6 +69379,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66566,20 +69390,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66596,6 +69416,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66605,20 +69427,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from the merge queue. - */ "pull-request/dequeued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66635,6 +69453,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66644,20 +69464,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66674,6 +69490,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66683,20 +69501,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to the merge queue. - */ "pull-request/enqueued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66713,6 +69527,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66722,20 +69538,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66752,6 +69564,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66761,20 +69575,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66791,6 +69601,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66800,20 +69612,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66830,6 +69638,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66839,20 +69649,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66869,6 +69675,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66878,20 +69686,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66908,6 +69712,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66917,20 +69723,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66947,6 +69749,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66956,20 +69760,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66986,6 +69786,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66995,20 +69797,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67025,6 +69823,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67034,20 +69834,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67064,6 +69860,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67073,20 +69871,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-cloud@latest//rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67103,6 +69897,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67112,20 +69908,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-cloud@latest//rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67142,6 +69934,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67151,20 +69945,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67181,6 +69971,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67190,20 +69982,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67220,6 +70008,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67229,20 +70019,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-cloud@latest//rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67259,6 +70045,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67268,20 +70056,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67298,6 +70082,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67307,20 +70093,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-cloud@latest//rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67337,6 +70119,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67346,20 +70130,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67376,6 +70156,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67385,20 +70167,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67415,6 +70193,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67424,20 +70204,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67454,6 +70230,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67463,20 +70241,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-cloud@latest//rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-cloud@latest//communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67493,6 +70267,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67502,22 +70278,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67534,6 +70304,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67543,21 +70315,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67574,6 +70341,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67583,21 +70352,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-cloud@latest//packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-cloud@latest//rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67614,6 +70378,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67623,18 +70389,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67651,6 +70415,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67660,18 +70426,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67688,6 +70452,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67697,18 +70463,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67725,6 +70489,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67734,18 +70500,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67762,6 +70526,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67771,18 +70537,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67799,6 +70563,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67808,18 +70574,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67836,6 +70600,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67845,18 +70611,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-cloud@latest//repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-cloud@latest//rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67873,6 +70637,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67882,18 +70648,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/enterprise-cloud@latest//code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. - * @description A repository security advisory was published. - */ "repository-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67910,6 +70674,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67919,18 +70685,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/enterprise-cloud@latest//code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. - * @description A private vulnerability report was submitted. - */ "repository-advisory/reported": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67947,6 +70711,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67956,18 +70722,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67984,6 +70748,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67993,18 +70759,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68021,6 +70785,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68030,18 +70796,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68058,6 +70822,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68067,17 +70833,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-cloud@latest//rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68094,6 +70859,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68103,18 +70870,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68131,6 +70896,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68140,13 +70907,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a repository is imported to GitHub Enterprise Cloud. For more information, see "[Importing a repository with GitHub Importer](https://docs.github.com/enterprise-cloud@latest//get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." For more information about the API to manage imports, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/migrations/source-imports). */ "repository-import": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68163,6 +70933,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68172,18 +70944,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68200,6 +70970,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68209,18 +70981,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68237,6 +71007,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68246,18 +71018,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68274,6 +71044,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68283,20 +71055,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was created. - */ "repository-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68313,6 +71081,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68322,20 +71092,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was deleted. - */ "repository-ruleset/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68352,6 +71118,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68361,20 +71129,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-cloud@latest//repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-cloud@latest//rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-cloud@latest//rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was edited. - */ "repository-ruleset/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68391,6 +71155,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68400,18 +71166,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68428,6 +71192,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68437,18 +71203,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-cloud@latest//repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-cloud@latest//rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68465,6 +71229,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68474,19 +71240,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68503,6 +71266,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68512,19 +71277,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68541,6 +71303,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68550,19 +71314,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68579,6 +71340,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68588,19 +71351,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68617,6 +71377,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68626,20 +71388,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68656,6 +71414,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68665,22 +71425,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68697,6 +71451,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68706,20 +71462,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68736,6 +71488,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68745,20 +71499,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68775,6 +71525,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68784,20 +71536,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-cloud@latest//code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-cloud@latest//rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was validated. - */ "secret-scanning-alert/validated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68814,6 +71562,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68823,18 +71573,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-cloud@latest//code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68851,6 +71599,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68860,18 +71610,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-cloud@latest//code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68888,6 +71636,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68897,18 +71647,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-cloud@latest//code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-cloud@latest//rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-cloud@latest//code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68925,6 +71673,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68934,17 +71684,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-cloud@latest//code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68961,6 +71710,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68970,20 +71721,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69000,6 +71747,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69009,18 +71758,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69037,6 +71784,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69046,18 +71795,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69074,6 +71821,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69083,20 +71832,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69113,6 +71858,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69122,18 +71869,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69150,6 +71895,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69159,18 +71906,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-cloud@latest//sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-cloud@latest//sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69187,6 +71932,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69196,18 +71943,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-cloud@latest//get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-cloud@latest//rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69224,6 +71969,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69233,18 +71980,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-cloud@latest//get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-cloud@latest//rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69261,6 +72006,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69270,17 +72017,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-cloud@latest//pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-cloud@latest//rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69297,6 +72043,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69306,20 +72054,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A parent issue was added to an issue. - */ "sub-issues/parent-issue-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69336,6 +72080,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69345,20 +72091,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A parent issue was removed from an issue. - */ "sub-issues/parent-issue-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69375,6 +72117,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69384,20 +72128,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A sub-issue was added to an issue. - */ "sub-issues/sub-issue-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69414,6 +72154,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69423,20 +72165,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A sub-issue was removed from an issue. - */ "sub-issues/sub-issue-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69453,6 +72191,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69462,20 +72202,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69492,6 +72228,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69501,19 +72239,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69530,6 +72265,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69539,19 +72276,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69568,6 +72302,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69577,19 +72313,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69606,6 +72339,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69615,19 +72350,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69644,6 +72376,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69653,19 +72387,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-cloud@latest//organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69682,6 +72413,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69691,18 +72424,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-cloud@latest//account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-cloud@latest//rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69719,6 +72450,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69728,19 +72461,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-cloud@latest//actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69757,6 +72487,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69766,20 +72498,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69796,6 +72524,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69805,20 +72535,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69835,6 +72561,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69844,20 +72572,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69874,6 +72598,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69883,20 +72609,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-cloud@latest//actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69913,6 +72635,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69922,20 +72646,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-cloud@latest//actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69952,6 +72672,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69961,20 +72683,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-cloud@latest//actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69991,6 +72709,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -70000,20 +72720,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-cloud@latest//actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-cloud@latest//graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-cloud@latest//rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -70030,6 +72746,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -70039,7 +72757,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types-ghes-3.10/types.d.ts b/packages/openapi-webhooks-types-ghes-3.10/types.d.ts index 1e07aee..43b377f 100644 --- a/packages/openapi-webhooks-types-ghes-3.10/types.d.ts +++ b/packages/openapi-webhooks-types-ghes-3.10/types.d.ts @@ -3,2494 +3,5369 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.10/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.10/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.10/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.10/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.10/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.10/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "cache-sync": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.10/admin/enterprise-management/caching-repositories/about-repository-caching)." */ post: operations["cache-sync"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.10/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.10/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.10/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.10/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.10/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.10/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.10/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.10/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.10/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.10/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.10/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.10/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.10/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.10/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.10/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was disabled. */ post: operations["enterprise/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.10/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was enabled. */ post: operations["enterprise/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.10/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.10/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.10/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.10/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.10/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.10/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.10/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.10/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.10/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.10/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.10/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.10/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.10/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.10/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.10/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.10/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.10/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.10/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.10/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.10/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.10/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.10/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.10/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.10/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.10/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.10/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.10/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.10/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.10/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.10/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.10/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.10/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.10/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.10/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.10/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.10/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.10/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.10/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.10/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.10/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.10/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.10/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.10/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.10/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.10/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.10/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was added to the enterprise. */ post: operations["user/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was removed from the enterprise. */ post: operations["user/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.10/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.10/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.10/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.10/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.10/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.10/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.10/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection rule created event */ @@ -2507,8 +5382,8 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.10/admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.10/admin/overview/about-enterprise-accounts)." */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2537,8 +5412,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.10/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.10/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2549,7 +5424,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2571,7 +5446,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -2836,34 +5711,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -2901,34 +5776,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3245,9 +6120,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3255,7 +6130,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5309,10 +8185,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5346,16 +8222,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5365,7 +8241,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5379,14 +8255,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5396,7 +8272,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5420,8 +8296,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5439,37 +8315,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert dismissed event */ "webhook-dependabot-alert-dismissed": { /** @enum {string} */ @@ -6159,14 +9035,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -7940,7 +10813,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -8879,8 +11753,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9494,7 +12368,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -9688,11 +12562,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -9755,11 +12633,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -16825,7 +19703,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -18988,7 +21866,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20542,19 +23420,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -21737,26 +24612,21 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -22156,17 +25026,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22233,7 +25103,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22241,9 +25111,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22253,8 +25123,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22503,17 +25373,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22580,7 +25450,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22588,9 +25458,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22600,8 +25470,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22824,9 +25694,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -22861,8 +25730,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -22912,9 +25781,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -23379,17 +26247,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23456,7 +26324,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23464,9 +26332,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23476,8 +26344,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23726,17 +26594,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23803,7 +26671,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23811,9 +26679,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23823,8 +26691,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24047,9 +26915,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24084,8 +26951,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24135,9 +27002,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -24601,17 +27467,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24678,7 +27544,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24686,9 +27552,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24698,8 +27564,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24945,17 +27811,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25022,7 +27888,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25030,9 +27896,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25042,8 +27908,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25266,9 +28132,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -25303,8 +28168,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -25354,9 +28219,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25496,31 +28360,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25897,17 +28761,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25974,7 +28838,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25982,17 +28846,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26241,17 +29105,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26318,7 +29182,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26326,17 +29190,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26559,9 +29423,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26596,8 +29459,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -26647,9 +29510,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27141,17 +30003,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27218,7 +30080,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27226,9 +30088,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27238,8 +30100,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27488,17 +30350,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27565,7 +30427,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27573,9 +30435,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27585,8 +30447,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27809,9 +30671,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27846,8 +30707,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -27897,9 +30758,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28362,17 +31222,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28439,7 +31299,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28447,9 +31307,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28459,8 +31319,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28709,17 +31569,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28786,7 +31646,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28794,9 +31654,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28806,8 +31666,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29030,9 +31890,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29067,8 +31926,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -29118,9 +31977,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29782,17 +32640,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29859,7 +32717,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29867,9 +32725,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29879,8 +32737,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30122,17 +32980,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30199,7 +33057,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30207,9 +33065,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30219,8 +33077,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30398,9 +33256,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30435,8 +33292,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -30486,9 +33343,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -30943,17 +33799,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31020,7 +33876,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31028,9 +33884,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31040,8 +33896,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31283,17 +34139,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31360,7 +34216,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31368,9 +34224,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31380,8 +34236,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31559,9 +34415,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31596,8 +34451,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -31647,9 +34502,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32259,17 +35113,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32336,7 +35190,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32344,9 +35198,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32356,8 +35210,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32599,17 +35453,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32676,7 +35530,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32684,9 +35538,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32696,8 +35550,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32875,9 +35729,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -32912,8 +35765,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -32963,9 +35816,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33420,17 +36272,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33497,7 +36349,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33505,9 +36357,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33517,8 +36369,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33760,17 +36612,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33837,7 +36689,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33845,9 +36697,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33857,8 +36709,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34036,9 +36888,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34073,8 +36924,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -34124,9 +36975,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34724,7 +37574,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35015,7 +37865,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35187,9 +38037,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35224,8 +38073,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -35275,9 +38124,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35466,9 +38314,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -35819,17 +38666,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35896,7 +38743,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36159,17 +39006,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36236,7 +39083,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36244,9 +39091,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36256,8 +39103,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36480,9 +39327,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36517,8 +39363,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -36568,9 +39414,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -36718,8 +39563,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -37070,17 +39915,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37147,7 +39992,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37155,9 +40000,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37167,8 +40012,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37417,17 +40262,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37494,7 +40339,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37502,9 +40347,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37514,8 +40359,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37738,9 +40583,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -37775,8 +40619,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37826,9 +40670,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -37994,13 +40837,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -38351,17 +41191,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38428,7 +41268,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38436,9 +41276,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38448,8 +41288,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -38698,17 +41538,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38775,7 +41615,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38783,9 +41623,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38795,8 +41635,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39019,9 +41859,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39056,8 +41895,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39107,9 +41946,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39257,8 +42095,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -39609,17 +42447,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39686,7 +42524,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39694,9 +42532,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39706,8 +42544,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39956,17 +42794,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40033,7 +42871,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40041,9 +42879,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40053,8 +42891,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40277,9 +43115,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40314,8 +43151,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -40365,9 +43202,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40533,9 +43369,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -40885,17 +43719,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40962,7 +43796,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40970,9 +43804,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40982,8 +43816,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41225,17 +44059,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41302,7 +44136,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41310,9 +44144,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41322,8 +44156,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41501,9 +44335,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -41538,8 +44371,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -41589,9 +44422,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42107,7 +44939,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42405,7 +45237,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42579,9 +45411,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42616,8 +45447,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42667,9 +45498,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43337,7 +46167,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43635,7 +46465,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43809,9 +46639,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43846,8 +46675,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -43897,9 +46726,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44511,17 +47339,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44588,7 +47416,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44596,9 +47424,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44608,8 +47436,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -44928,7 +47756,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44936,9 +47764,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44948,8 +47776,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45172,9 +48000,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45209,8 +48036,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45260,9 +48087,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45726,17 +48552,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -45803,7 +48629,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45811,9 +48637,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45823,8 +48649,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46073,17 +48899,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46150,7 +48976,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46158,9 +48984,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46170,8 +48996,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46394,9 +49220,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46431,8 +49256,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46482,9 +49307,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -46948,17 +49772,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -47025,7 +49849,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47033,9 +49857,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47045,8 +49869,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47365,7 +50189,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47373,9 +50197,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47385,8 +50209,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47609,9 +50433,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -47646,8 +50469,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -47697,9 +50520,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48162,17 +50984,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48239,7 +51061,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48247,9 +51069,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48259,8 +51081,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48509,17 +51331,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48586,7 +51408,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48594,9 +51416,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48606,8 +51428,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48830,9 +51652,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -48867,8 +51688,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -48918,9 +51739,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49376,7 +52196,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49499,19 +52319,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -49524,7 +52348,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -49536,21 +52361,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -51203,34 +54026,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -51442,34 +54265,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52213,7 +55036,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52461,7 +55284,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52709,7 +55532,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52988,7 +55811,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53236,7 +56059,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -55038,20 +57861,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.10/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.10/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55072,6 +57886,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55081,18 +57897,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.10/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.10/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55113,6 +57927,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55122,18 +57938,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.10/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.10/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55154,6 +57968,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55163,13 +57979,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.10/admin/enterprise-management/caching-repositories/about-repository-caching)." */ "cache-sync": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55190,6 +58009,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55199,25 +58020,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55238,6 +58050,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55247,25 +58061,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55286,6 +58091,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55295,25 +58102,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.10/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55334,6 +58132,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55343,25 +58143,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.10/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55382,6 +58173,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55391,25 +58184,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.10/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55430,6 +58214,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55439,25 +58225,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.10/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.10/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.10/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55478,6 +58255,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55487,25 +58266,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.10/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.10/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.10/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.10/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55526,6 +58296,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55535,18 +58307,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55567,6 +58337,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55576,18 +58348,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55608,6 +58378,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55617,18 +58389,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55649,6 +58419,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55658,18 +58430,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55690,6 +58460,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55699,18 +58471,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55731,6 +58501,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55740,18 +58512,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.10/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.10/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55772,6 +58542,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55781,20 +58553,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.10/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55815,6 +58583,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55824,21 +58594,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55859,6 +58624,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55868,21 +58635,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55903,6 +58665,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55912,23 +58676,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55949,6 +58706,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55958,23 +58717,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55995,6 +58747,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56004,23 +58758,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56041,6 +58788,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56050,23 +58799,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56087,6 +58829,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56096,23 +58840,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.10/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56133,6 +58870,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56142,18 +58881,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.10/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.10/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56174,6 +58911,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56183,18 +58922,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.10/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.10/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56215,6 +58952,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56224,20 +58963,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56258,6 +58993,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56267,18 +59004,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.10/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56299,6 +59034,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56308,20 +59045,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56342,6 +59075,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56351,20 +59086,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56385,6 +59116,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56394,20 +59127,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56428,6 +59157,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56437,23 +59168,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.10/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.10/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56474,6 +59198,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56483,23 +59209,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56520,6 +59239,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56529,23 +59250,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56566,6 +59280,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56575,23 +59291,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56612,6 +59321,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56621,23 +59332,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56658,6 +59362,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56667,23 +59373,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56704,6 +59403,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56713,23 +59414,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56750,6 +59444,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56759,23 +59455,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56796,6 +59485,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56805,23 +59496,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56842,6 +59526,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56851,23 +59537,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56888,6 +59567,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56897,23 +59578,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56934,6 +59608,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56943,23 +59619,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56980,6 +59649,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56989,23 +59660,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57026,6 +59690,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57035,23 +59701,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57072,6 +59731,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57081,23 +59742,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57118,6 +59772,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57127,23 +59783,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57164,6 +59813,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57173,23 +59824,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57210,6 +59854,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57219,23 +59865,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57256,6 +59895,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57265,23 +59906,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.10/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57302,6 +59936,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57311,16 +59947,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.10/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was disabled. - */ "enterprise/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57341,6 +59977,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57350,16 +59988,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.10/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was enabled. - */ "enterprise/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57380,6 +60018,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57389,17 +60029,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.10/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.10/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57420,6 +60059,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57429,20 +60070,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.10/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57463,6 +60100,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57472,17 +60111,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.10/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57503,6 +60141,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57512,18 +60152,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57544,6 +60182,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57553,18 +60193,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57585,6 +60223,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57594,18 +60234,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57626,6 +60264,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57635,18 +60275,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57667,6 +60305,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57676,18 +60316,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57708,6 +60346,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57717,18 +60357,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57749,6 +60387,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57758,16 +60398,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57788,6 +60428,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57797,18 +60439,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.10/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.10/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57829,6 +60469,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57838,20 +60480,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.10/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57872,6 +60510,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57881,20 +60521,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.10/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57915,6 +60551,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57924,20 +60562,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.10/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.10/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57958,6 +60592,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57967,20 +60603,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58001,6 +60633,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58010,20 +60644,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58044,6 +60674,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58053,20 +60685,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58087,6 +60715,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58096,20 +60726,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58130,6 +60756,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58139,20 +60767,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58173,6 +60797,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58182,20 +60808,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58216,6 +60838,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58225,20 +60849,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58259,6 +60879,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58268,20 +60890,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58302,6 +60920,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58311,20 +60931,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58345,6 +60961,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58354,20 +60972,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58388,6 +61002,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58397,20 +61013,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58431,6 +61043,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58440,20 +61054,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58474,6 +61084,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58483,20 +61095,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58517,6 +61125,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58526,20 +61136,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58560,6 +61166,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58569,20 +61177,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58603,6 +61207,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58612,20 +61218,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.10/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.10/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58646,6 +61248,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58655,20 +61259,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.10/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58689,6 +61289,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58698,20 +61300,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.10/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58732,6 +61330,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58741,20 +61341,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.10/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58775,6 +61371,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58784,18 +61382,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.10/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.10/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58816,6 +61412,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58825,18 +61423,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.10/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.10/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58857,6 +61453,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58866,18 +61464,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.10/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.10/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58898,6 +61494,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58907,18 +61505,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.10/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58939,6 +61535,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58948,18 +61546,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.10/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58980,6 +61576,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58989,18 +61587,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59021,6 +61617,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59030,20 +61628,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59064,6 +61658,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59073,20 +61669,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59107,6 +61699,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59116,20 +61710,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59150,6 +61740,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59159,20 +61751,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59193,6 +61781,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59202,20 +61792,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.10/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.10/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59236,6 +61822,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59245,20 +61833,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59279,6 +61863,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59288,20 +61874,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59322,6 +61904,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59331,20 +61915,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59365,6 +61945,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59374,20 +61956,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59408,6 +61986,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59417,20 +61997,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.10/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.10/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59451,6 +62027,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59460,18 +62038,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59492,6 +62068,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59501,18 +62079,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59533,6 +62109,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59542,17 +62120,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.10/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.10/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59573,6 +62150,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59582,21 +62161,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59613,6 +62187,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59622,21 +62198,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59653,6 +62224,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59662,21 +62235,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59693,6 +62261,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59702,21 +62272,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.10/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59733,6 +62298,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59742,13 +62309,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59769,6 +62339,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59778,22 +62350,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59814,6 +62380,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59823,22 +62391,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59859,6 +62421,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59868,22 +62432,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59904,6 +62462,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59913,22 +62473,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59949,6 +62503,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59958,22 +62514,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59994,6 +62544,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60003,22 +62555,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60039,6 +62585,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60048,22 +62596,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60084,6 +62626,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60093,22 +62637,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60129,6 +62667,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60138,22 +62678,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60174,6 +62708,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60183,22 +62719,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60219,6 +62749,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60228,22 +62760,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60264,6 +62790,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60273,22 +62801,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60309,6 +62831,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60318,22 +62842,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60354,6 +62872,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60363,22 +62883,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.10/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.10/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60399,6 +62913,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60408,23 +62924,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60445,6 +62954,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60454,23 +62965,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60491,6 +62995,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60500,23 +63006,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60537,6 +63036,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60546,23 +63047,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60583,6 +63077,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60592,23 +63088,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60629,6 +63118,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60638,23 +63129,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60675,6 +63159,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60684,23 +63170,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60721,6 +63200,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60730,23 +63211,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60767,6 +63241,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60776,23 +63252,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60813,6 +63282,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60822,23 +63293,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60859,6 +63323,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60868,23 +63334,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60905,6 +63364,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60914,23 +63375,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.10/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60951,6 +63405,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60960,17 +63416,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.10/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60991,6 +63446,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61000,20 +63457,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61034,6 +63487,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61043,20 +63498,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61077,6 +63528,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61086,20 +63539,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61120,6 +63569,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61129,20 +63580,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61163,6 +63610,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61172,20 +63621,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61206,6 +63651,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61215,20 +63662,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61249,6 +63692,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61258,20 +63703,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61292,6 +63733,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61301,20 +63744,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61335,6 +63774,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61344,20 +63785,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61378,6 +63815,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61387,20 +63826,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61421,6 +63856,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61430,20 +63867,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61464,6 +63897,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61473,20 +63908,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61507,6 +63938,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61516,20 +63949,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61550,6 +63979,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61559,20 +63990,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61593,6 +64020,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61602,20 +64031,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61636,6 +64061,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61645,20 +64072,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61679,6 +64102,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61688,20 +64113,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.10/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61722,6 +64143,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61731,20 +64154,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.10/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61765,6 +64184,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61774,20 +64195,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61808,6 +64225,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61817,20 +64236,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61851,6 +64266,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61860,20 +64277,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.10/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61894,6 +64307,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61903,20 +64318,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61937,6 +64348,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61946,20 +64359,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.10/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61980,6 +64389,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61989,20 +64400,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62023,6 +64430,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62032,20 +64441,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62066,6 +64471,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62075,20 +64482,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62109,6 +64512,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62118,20 +64523,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.10/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.10/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62152,6 +64553,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62161,22 +64564,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62197,6 +64594,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62206,21 +64605,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62241,6 +64635,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62250,21 +64646,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.10/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.10/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62285,6 +64676,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62294,18 +64687,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62326,6 +64717,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62335,18 +64728,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62367,6 +64758,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62376,18 +64769,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62408,6 +64799,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62417,18 +64810,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62449,6 +64840,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62458,18 +64851,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62490,6 +64881,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62499,18 +64892,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62531,6 +64922,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62540,18 +64933,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.10/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.10/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62572,6 +64963,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62581,18 +64974,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62613,6 +65004,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62622,18 +65015,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62654,6 +65045,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62663,18 +65056,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62695,6 +65086,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62704,18 +65097,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62736,6 +65127,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62745,18 +65138,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62777,6 +65168,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62786,17 +65179,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.10/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62817,6 +65209,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62826,18 +65220,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62858,6 +65250,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62867,18 +65261,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62899,6 +65291,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62908,18 +65302,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62940,6 +65332,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62949,18 +65343,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62981,6 +65373,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62990,18 +65384,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63022,6 +65414,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63031,18 +65425,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.10/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.10/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63063,6 +65455,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63072,19 +65466,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63105,6 +65496,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63114,19 +65507,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63147,6 +65537,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63156,19 +65548,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63189,6 +65578,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63198,19 +65589,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63231,6 +65619,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63240,20 +65630,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63274,6 +65660,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63283,22 +65671,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63319,6 +65701,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63328,20 +65712,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63362,6 +65742,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63371,20 +65753,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.10/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.10/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63405,6 +65783,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63414,18 +65794,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.10/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63446,6 +65824,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63455,18 +65835,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.10/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63487,6 +65865,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63496,18 +65876,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.10/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.10/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.10/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63528,6 +65906,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63537,17 +65917,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.10/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63568,6 +65947,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63577,20 +65958,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63611,6 +65988,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63620,18 +65999,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63652,6 +66029,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63661,18 +66040,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63693,6 +66070,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63702,20 +66081,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63736,6 +66111,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63745,18 +66122,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63777,6 +66152,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63786,18 +66163,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.10/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.10/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63818,6 +66193,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63827,18 +66204,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.10/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.10/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63859,6 +66234,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63868,18 +66245,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.10/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.10/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63900,6 +66275,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63909,17 +66286,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.10/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.10/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63940,6 +66316,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63949,20 +66327,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.10/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63983,6 +66357,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63992,19 +66368,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64025,6 +66398,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64034,19 +66409,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64067,6 +66439,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64076,19 +66450,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64109,6 +66480,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64118,19 +66491,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64151,6 +66521,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64160,19 +66532,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.10/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64193,6 +66562,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64202,16 +66573,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was added to the enterprise. - */ "user/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64232,6 +66603,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64241,16 +66614,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was removed from the enterprise. - */ "user/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64271,6 +66644,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64280,18 +66655,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.10/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.10/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64312,6 +66685,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64321,19 +66696,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.10/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64354,6 +66726,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64363,20 +66737,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64397,6 +66767,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64406,20 +66778,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64440,6 +66808,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64449,20 +66819,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64483,6 +66849,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64492,20 +66860,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.10/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64526,6 +66890,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64535,20 +66901,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.10/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64569,6 +66931,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64578,20 +66942,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.10/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64612,6 +66972,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64621,20 +66983,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.10/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.10/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.10/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64655,6 +67013,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64664,7 +67024,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types-ghes-3.11/types.d.ts b/packages/openapi-webhooks-types-ghes-3.11/types.d.ts index c3e2bd0..6605fe9 100644 --- a/packages/openapi-webhooks-types-ghes-3.11/types.d.ts +++ b/packages/openapi-webhooks-types-ghes-3.11/types.d.ts @@ -3,2549 +3,5489 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-configuration-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were disabled for a repository. */ post: operations["branch-protection-configuration/disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-configuration-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were enabled for a repository. */ post: operations["branch-protection-configuration/enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "cache-sync": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.11/admin/enterprise-management/caching-repositories/about-repository-caching)." */ post: operations["cache-sync"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.11/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.11/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.11/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.11/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.11/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.11/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.11/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.11/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.11/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.11/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.11/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.11/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.11/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.11/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.11/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was disabled. */ post: operations["enterprise/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.11/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was enabled. */ post: operations["enterprise/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.11/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.11/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.11/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.11/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.11/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.11/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.11/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.11/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.11/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.11/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.11/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.11/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.11/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.11/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.11/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.11/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.11/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.11/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.11/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.11/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.11/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.11/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.11/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.11/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.11/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.11/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.11/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.11/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.11/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.11/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.11/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.11/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.11/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was created. */ post: operations["repository-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was deleted. */ post: operations["repository-ruleset/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was edited. */ post: operations["repository-ruleset/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.11/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.11/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.11/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.11/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.11/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.11/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.11/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.11/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.11/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.11/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.11/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.11/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.11/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was added to the enterprise. */ post: operations["user/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was removed from the enterprise. */ post: operations["user/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.11/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.11/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.11/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.11/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.11/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.11/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.11/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection configuration disabled event */ @@ -2561,8 +5501,8 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.11/admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.11/admin/overview/about-enterprise-accounts)." */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2591,8 +5531,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.11/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.11/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2603,7 +5543,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2625,7 +5565,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -2890,34 +5830,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -2955,34 +5895,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3320,9 +6260,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3330,7 +6270,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5384,10 +8325,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5421,16 +8362,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5440,7 +8381,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5454,14 +8395,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5471,7 +8412,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5495,8 +8436,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5514,37 +8455,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert dismissed event */ "webhook-dependabot-alert-dismissed": { /** @enum {string} */ @@ -6234,14 +9175,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -8015,7 +10953,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -8954,8 +11893,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9569,7 +12508,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -9763,11 +12702,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -9830,11 +12773,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -16901,7 +19844,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19064,7 +22007,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20618,19 +23561,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -21813,26 +24753,21 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -22232,17 +25167,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22309,7 +25244,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22317,9 +25252,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22329,8 +25264,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22579,17 +25514,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22656,7 +25591,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22664,9 +25599,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22676,8 +25611,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22900,9 +25835,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -22937,8 +25871,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -22988,9 +25922,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -23455,17 +26388,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23532,7 +26465,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23540,9 +26473,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23552,8 +26485,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23802,17 +26735,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23879,7 +26812,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23887,9 +26820,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23899,8 +26832,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24123,9 +27056,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24160,8 +27092,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24211,9 +27143,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -24677,17 +27608,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24754,7 +27685,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24762,9 +27693,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24774,8 +27705,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25021,17 +27952,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25098,7 +28029,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25106,9 +28037,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25118,8 +28049,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25342,9 +28273,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -25379,8 +28309,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -25430,9 +28360,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25572,31 +28501,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25973,17 +28902,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26050,7 +28979,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26058,17 +28987,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26317,17 +29246,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26394,7 +29323,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26402,17 +29331,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26635,9 +29564,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26672,8 +29600,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -26723,9 +29651,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27217,17 +30144,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27294,7 +30221,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27302,9 +30229,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27314,8 +30241,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27564,17 +30491,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27641,7 +30568,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27649,9 +30576,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27661,8 +30588,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27885,9 +30812,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27922,8 +30848,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -27973,9 +30899,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28438,17 +31363,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28515,7 +31440,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28523,9 +31448,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28535,8 +31460,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28785,17 +31710,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28862,7 +31787,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28870,9 +31795,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28882,8 +31807,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29106,9 +32031,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29143,8 +32067,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -29194,9 +32118,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29858,17 +32781,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29935,7 +32858,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29943,9 +32866,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29955,8 +32878,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30198,17 +33121,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30275,7 +33198,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30283,9 +33206,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30295,8 +33218,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30474,9 +33397,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30511,8 +33433,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -30562,9 +33484,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -31019,17 +33940,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31096,7 +34017,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31104,9 +34025,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31116,8 +34037,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31359,17 +34280,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31436,7 +34357,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31444,9 +34365,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31456,8 +34377,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31635,9 +34556,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31672,8 +34592,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -31723,9 +34643,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32335,17 +35254,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32412,7 +35331,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32420,9 +35339,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32432,8 +35351,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32675,17 +35594,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32752,7 +35671,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32760,9 +35679,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32772,8 +35691,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32951,9 +35870,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -32988,8 +35906,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -33039,9 +35957,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33496,17 +36413,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33573,7 +36490,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33581,9 +36498,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33593,8 +36510,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33836,17 +36753,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33913,7 +36830,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33921,9 +36838,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33933,8 +36850,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34112,9 +37029,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34149,8 +37065,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -34200,9 +37116,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34800,7 +37715,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35091,7 +38006,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35263,9 +38178,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35300,8 +38214,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -35351,9 +38265,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35542,9 +38455,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -35895,17 +38807,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35972,7 +38884,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36235,17 +39147,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36312,7 +39224,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36320,9 +39232,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36332,8 +39244,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36556,9 +39468,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36593,8 +39504,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -36644,9 +39555,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -36794,8 +39704,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -37146,17 +40056,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37223,7 +40133,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37231,9 +40141,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37243,8 +40153,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37493,17 +40403,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37570,7 +40480,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37578,9 +40488,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37590,8 +40500,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37814,9 +40724,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -37851,8 +40760,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37902,9 +40811,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38070,13 +40978,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -38427,17 +41332,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38504,7 +41409,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38512,9 +41417,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38524,8 +41429,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -38774,17 +41679,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38851,7 +41756,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38859,9 +41764,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38871,8 +41776,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39095,9 +42000,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39132,8 +42036,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39183,9 +42087,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39333,8 +42236,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -39685,17 +42588,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39762,7 +42665,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39770,9 +42673,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39782,8 +42685,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40032,17 +42935,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40109,7 +43012,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40117,9 +43020,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40129,8 +43032,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40353,9 +43256,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40390,8 +43292,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -40441,9 +43343,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40609,9 +43510,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -40961,17 +43860,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41038,7 +43937,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41046,9 +43945,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41058,8 +43957,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41301,17 +44200,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41378,7 +44277,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41386,9 +44285,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41398,8 +44297,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41577,9 +44476,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -41614,8 +44512,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -41665,9 +44563,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42183,7 +45080,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42481,7 +45378,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42655,9 +45552,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42692,8 +45588,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42743,9 +45639,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43413,7 +46308,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43711,7 +46606,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43885,9 +46780,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43922,8 +46816,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -43973,9 +46867,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44587,17 +47480,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44664,7 +47557,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44672,9 +47565,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44684,8 +47577,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45004,7 +47897,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45012,9 +47905,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45024,8 +47917,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45248,9 +48141,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45285,8 +48177,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45336,9 +48228,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45802,17 +48693,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -45879,7 +48770,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45887,9 +48778,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45899,8 +48790,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46149,17 +49040,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46226,7 +49117,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46234,9 +49125,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46246,8 +49137,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46470,9 +49361,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46507,8 +49397,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46558,9 +49448,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -47024,17 +49913,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -47101,7 +49990,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47109,9 +49998,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47121,8 +50010,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47441,7 +50330,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47449,9 +50338,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47461,8 +50350,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47685,9 +50574,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -47722,8 +50610,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -47773,9 +50661,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48238,17 +51125,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48315,7 +51202,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48323,9 +51210,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48335,8 +51222,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48585,17 +51472,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48662,7 +51549,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48670,9 +51557,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48682,8 +51569,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48906,9 +51793,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -48943,8 +51829,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -48994,9 +51880,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49452,7 +52337,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49575,19 +52460,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -49600,7 +52489,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -49612,21 +52502,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -50524,7 +53412,7 @@ export interface components { bypass_actors?: components["schemas"]["repository-ruleset-bypass-actor"][]; /** * @description The bypass type of the user making the API request for this ruleset. This field is only returned when - * querying the repository-level endpoint. + * querying the repository-level endpoint. * @enum {string} */ current_user_can_bypass?: "always" | "pull_requests_only" | "never"; @@ -50540,11 +53428,15 @@ export interface components { }; }; conditions?: - | null | ( - | components["schemas"]["repository-ruleset-conditions"] - | components["schemas"]["org-ruleset-conditions"] - ); + | null + | ( + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"] + ) + ) + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"]; rules?: components["schemas"]["repository-rule"][]; /** Format: date-time */ created_at?: string; @@ -50594,6 +53486,7 @@ export interface components { /** * Organization ruleset conditions * @description Conditions for an organization ruleset. The conditions object should contain both `repository_name` and `ref_name` properties or both `repository_id` and `ref_name` properties. + * */ "org-ruleset-conditions": | (components["schemas"]["repository-ruleset-conditions"] & @@ -51748,34 +54641,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -51987,34 +54880,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52758,7 +55651,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53006,7 +55899,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53254,7 +56147,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53533,7 +56426,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53781,7 +56674,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -55583,22 +58476,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were disabled for a repository. - */ "branch-protection-configuration/disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55615,6 +58497,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55624,20 +58508,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were enabled for a repository. - */ "branch-protection-configuration/enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55654,6 +58534,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55663,18 +58545,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55695,6 +58575,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55704,18 +58586,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55736,6 +58616,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55745,18 +58627,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.11/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55777,6 +58657,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55786,13 +58668,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.11/admin/enterprise-management/caching-repositories/about-repository-caching)." */ "cache-sync": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55813,6 +58698,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55822,25 +58709,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55861,6 +58739,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55870,25 +58750,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55909,6 +58780,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55918,25 +58791,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.11/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55957,6 +58821,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55966,25 +58832,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.11/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56005,6 +58862,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56014,25 +58873,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.11/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56053,6 +58903,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56062,25 +58914,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.11/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.11/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.11/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56101,6 +58944,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56110,25 +58955,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; - }; - }; - }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.11/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.11/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.11/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.11/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ + headers: { + [name: string]: unknown; + }; + content?: never; + }; + }; + }; "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56149,6 +58985,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56158,18 +58996,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56190,6 +59026,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56199,18 +59037,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56231,6 +59067,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56240,18 +59078,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56272,6 +59108,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56281,18 +59119,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56313,6 +59149,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56322,18 +59160,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56354,6 +59190,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56363,18 +59201,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.11/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.11/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56395,6 +59231,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56404,20 +59242,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.11/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56438,6 +59272,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56447,21 +59283,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56482,6 +59313,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56491,21 +59324,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56526,6 +59354,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56535,23 +59365,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56572,6 +59395,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56581,23 +59406,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56618,6 +59436,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56627,23 +59447,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56664,6 +59477,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56673,23 +59488,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56710,6 +59518,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56719,23 +59529,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.11/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56756,6 +59559,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56765,18 +59570,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.11/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.11/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56797,6 +59600,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56806,18 +59611,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.11/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.11/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56838,6 +59641,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56847,20 +59652,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56881,6 +59682,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56890,18 +59693,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.11/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56922,6 +59723,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56931,20 +59734,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56965,6 +59764,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56974,20 +59775,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57008,6 +59805,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57017,20 +59816,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57051,6 +59846,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57060,23 +59857,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.11/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.11/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57097,6 +59887,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57106,23 +59898,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57143,6 +59928,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57152,23 +59939,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57189,6 +59969,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57198,23 +59980,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57235,6 +60010,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57244,23 +60021,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57281,6 +60051,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57290,23 +60062,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57327,6 +60092,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57336,23 +60103,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57373,6 +60133,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57382,23 +60144,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57419,6 +60174,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57428,23 +60185,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57465,6 +60215,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57474,23 +60226,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57511,6 +60256,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57520,23 +60267,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57557,6 +60297,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57566,23 +60308,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57603,6 +60338,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57612,23 +60349,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57649,6 +60379,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57658,23 +60390,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57695,6 +60420,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57704,23 +60431,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57741,6 +60461,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57750,23 +60472,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57787,6 +60502,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57796,23 +60513,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57833,6 +60543,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57842,23 +60554,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57879,6 +60584,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57888,23 +60595,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.11/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57925,6 +60625,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57934,16 +60636,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.11/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was disabled. - */ "enterprise/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57964,6 +60666,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57973,16 +60677,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.11/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was enabled. - */ "enterprise/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58003,6 +60707,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58012,17 +60718,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.11/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.11/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58043,6 +60748,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58052,20 +60759,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.11/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58086,6 +60789,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58095,17 +60800,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.11/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58126,6 +60830,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58135,18 +60841,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58167,6 +60871,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58176,18 +60882,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58208,6 +60912,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58217,18 +60923,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58249,6 +60953,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58258,18 +60964,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58290,6 +60994,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58299,18 +61005,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58331,6 +61035,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58340,18 +61046,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58372,6 +61076,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58381,16 +61087,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58411,6 +61117,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58420,18 +61128,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.11/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.11/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58452,6 +61158,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58461,20 +61169,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.11/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58495,6 +61199,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58504,20 +61210,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.11/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58538,6 +61240,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58547,20 +61251,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.11/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.11/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58581,6 +61281,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58590,20 +61292,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58624,6 +61322,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58633,20 +61333,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58667,6 +61363,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58676,20 +61374,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58710,6 +61404,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58719,20 +61415,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58753,6 +61445,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58762,20 +61456,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58796,6 +61486,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58805,20 +61497,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58839,6 +61527,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58848,20 +61538,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58882,6 +61568,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58891,20 +61579,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58925,6 +61609,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58934,20 +61620,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58968,6 +61650,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58977,20 +61661,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59011,6 +61691,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59020,20 +61702,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59054,6 +61732,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59063,20 +61743,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59097,6 +61773,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59106,20 +61784,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59140,6 +61814,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59149,20 +61825,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59183,6 +61855,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59192,20 +61866,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59226,6 +61896,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59235,20 +61907,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.11/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.11/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59269,6 +61937,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59278,20 +61948,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.11/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59312,6 +61978,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59321,20 +61989,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.11/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59355,6 +62019,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59364,20 +62030,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.11/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59398,6 +62060,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59407,18 +62071,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.11/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.11/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59439,6 +62101,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59448,18 +62112,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.11/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.11/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59480,6 +62142,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59489,18 +62153,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.11/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.11/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59521,6 +62183,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59530,18 +62194,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.11/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59562,6 +62224,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59571,18 +62235,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.11/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59603,6 +62265,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59612,18 +62276,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59644,6 +62306,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59653,20 +62317,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59687,6 +62347,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59696,20 +62358,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59730,6 +62388,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59739,20 +62399,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59773,6 +62429,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59782,20 +62440,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59816,6 +62470,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59825,20 +62481,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.11/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.11/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59859,6 +62511,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59868,20 +62522,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59902,6 +62552,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59911,20 +62563,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59945,6 +62593,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59954,20 +62604,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59988,6 +62634,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59997,20 +62645,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60031,6 +62675,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60040,20 +62686,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.11/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.11/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60074,6 +62716,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60083,18 +62727,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60115,6 +62757,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60124,18 +62768,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60156,6 +62798,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60165,17 +62809,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.11/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.11/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60196,6 +62839,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60205,21 +62850,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60236,6 +62876,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60245,21 +62887,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60276,6 +62913,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60285,21 +62924,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60316,6 +62950,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60325,21 +62961,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.11/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60356,6 +62987,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60365,13 +62998,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60392,6 +63028,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60401,22 +63039,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60437,6 +63069,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60446,22 +63080,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60482,6 +63110,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60491,22 +63121,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60527,6 +63151,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60536,22 +63162,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60572,6 +63192,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60581,22 +63203,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60617,6 +63233,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60626,22 +63244,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60662,6 +63274,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60671,22 +63285,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60707,6 +63315,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60716,22 +63326,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60752,6 +63356,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60761,22 +63367,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60797,6 +63397,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60806,22 +63408,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60842,6 +63438,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60851,22 +63449,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60887,6 +63479,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60896,22 +63490,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60932,6 +63520,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60941,22 +63531,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60977,6 +63561,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60986,22 +63572,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.11/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.11/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61022,6 +63602,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61031,23 +63613,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61068,6 +63643,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61077,23 +63654,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61114,6 +63684,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61123,23 +63695,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61160,6 +63725,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61169,23 +63736,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61206,6 +63766,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61215,23 +63777,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61252,6 +63807,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61261,23 +63818,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61298,6 +63848,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61307,23 +63859,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61344,6 +63889,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61353,23 +63900,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61390,6 +63930,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61399,23 +63941,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61436,6 +63971,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61445,23 +63982,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61482,6 +64012,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61491,23 +64023,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61528,6 +64053,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61537,23 +64064,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.11/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61574,6 +64094,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61583,17 +64105,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.11/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61614,6 +64135,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61623,20 +64146,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61657,6 +64176,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61666,20 +64187,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61700,6 +64217,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61709,20 +64228,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61743,6 +64258,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61752,20 +64269,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61786,6 +64299,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61795,20 +64310,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61829,6 +64340,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61838,20 +64351,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61872,6 +64381,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61881,20 +64392,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61915,6 +64422,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61924,20 +64433,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61958,6 +64463,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61967,20 +64474,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62001,6 +64504,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62010,20 +64515,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62044,6 +64545,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62053,20 +64556,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62087,6 +64586,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62096,20 +64597,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62130,6 +64627,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62139,20 +64638,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62173,6 +64668,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62182,20 +64679,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62216,6 +64709,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62225,20 +64720,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62259,6 +64750,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62268,20 +64761,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62302,6 +64791,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62311,20 +64802,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.11/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62345,6 +64832,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62354,20 +64843,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.11/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62388,6 +64873,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62397,20 +64884,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62431,6 +64914,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62440,20 +64925,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62474,6 +64955,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62483,20 +64966,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.11/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62517,6 +64996,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62526,20 +65007,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62560,6 +65037,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62569,20 +65048,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.11/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62603,6 +65078,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62612,20 +65089,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62646,6 +65119,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62655,20 +65130,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62689,6 +65160,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62698,20 +65171,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62732,6 +65201,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62741,20 +65212,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.11/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.11/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62775,6 +65242,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62784,22 +65253,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62820,6 +65283,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62829,21 +65294,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62864,6 +65324,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62873,21 +65335,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.11/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.11/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62908,6 +65365,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62917,18 +65376,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62949,6 +65406,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62958,18 +65417,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62990,6 +65447,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62999,18 +65458,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63031,6 +65488,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63040,18 +65499,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63072,6 +65529,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63081,18 +65540,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63113,6 +65570,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63122,18 +65581,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63154,6 +65611,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63163,18 +65622,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.11/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.11/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63195,6 +65652,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63204,18 +65663,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63236,6 +65693,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63245,18 +65704,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63277,6 +65734,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63286,18 +65745,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63318,6 +65775,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63327,18 +65786,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63359,6 +65816,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63368,18 +65827,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63400,6 +65857,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63409,17 +65868,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.11/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63440,6 +65898,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63449,18 +65909,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63481,6 +65939,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63490,18 +65950,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63522,6 +65980,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63531,18 +65991,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63563,6 +66021,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63572,18 +66032,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63604,6 +66062,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63613,20 +66073,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was created. - */ "repository-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63643,6 +66099,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63652,20 +66110,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was deleted. - */ "repository-ruleset/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63682,6 +66136,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63691,20 +66147,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.11/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.11/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.11/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was edited. - */ "repository-ruleset/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63721,6 +66173,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63730,18 +66184,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63762,6 +66214,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63771,18 +66225,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.11/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.11/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63803,6 +66255,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63812,19 +66266,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63845,6 +66296,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63854,19 +66307,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63887,6 +66337,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63896,19 +66348,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63929,6 +66378,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63938,19 +66389,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63971,6 +66419,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63980,20 +66430,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64014,6 +66460,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64023,22 +66471,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64059,6 +66501,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64068,20 +66512,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64102,6 +66542,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64111,20 +66553,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.11/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.11/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64145,6 +66583,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64154,18 +66594,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.11/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64186,6 +66624,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64195,18 +66635,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.11/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64227,6 +66665,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64236,18 +66676,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.11/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.11/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.11/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64268,6 +66706,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64277,17 +66717,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.11/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64308,6 +66747,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64317,20 +66758,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64351,6 +66788,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64360,18 +66799,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64392,6 +66829,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64401,18 +66840,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64433,6 +66870,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64442,20 +66881,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64476,6 +66911,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64485,18 +66922,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64517,6 +66952,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64526,18 +66963,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.11/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.11/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64558,6 +66993,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64567,18 +67004,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.11/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.11/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64599,6 +67034,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64608,18 +67045,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.11/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.11/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64640,6 +67075,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64649,17 +67086,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.11/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.11/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64680,6 +67116,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64689,20 +67127,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.11/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64723,6 +67157,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64732,19 +67168,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64765,6 +67198,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64774,19 +67209,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64807,6 +67239,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64816,19 +67250,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64849,6 +67280,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64858,19 +67291,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64891,6 +67321,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64900,19 +67332,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.11/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64933,6 +67362,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64942,16 +67373,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was added to the enterprise. - */ "user/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64972,6 +67403,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64981,16 +67414,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was removed from the enterprise. - */ "user/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65011,6 +67444,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65020,18 +67455,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.11/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.11/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65052,6 +67485,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65061,19 +67496,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.11/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65094,6 +67526,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65103,20 +67537,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65137,6 +67567,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65146,20 +67578,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65180,6 +67608,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65189,20 +67619,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65223,6 +67649,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65232,20 +67660,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.11/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65266,6 +67690,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65275,20 +67701,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.11/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65309,6 +67731,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65318,20 +67742,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.11/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65352,6 +67772,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65361,20 +67783,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.11/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.11/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.11/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65395,6 +67813,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65404,7 +67824,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types-ghes-3.12/types.d.ts b/packages/openapi-webhooks-types-ghes-3.12/types.d.ts index 576674d..cb36f3a 100644 --- a/packages/openapi-webhooks-types-ghes-3.12/types.d.ts +++ b/packages/openapi-webhooks-types-ghes-3.12/types.d.ts @@ -3,2577 +3,5543 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-configuration-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were disabled for a repository. */ post: operations["branch-protection-configuration/disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-configuration-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were enabled for a repository. */ post: operations["branch-protection-configuration/enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "cache-sync": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.12/admin/enterprise-management/caching-repositories/about-repository-caching)." */ post: operations["cache-sync"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.12/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.12/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.12/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.12/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.12/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.12/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.12/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.12/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.12/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. */ post: operations["dependabot-alert/auto-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. */ post: operations["dependabot-alert/auto-reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.12/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.12/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.12/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.12/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.12/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.12/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was disabled. */ post: operations["enterprise/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.12/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was enabled. */ post: operations["enterprise/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.12/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.12/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.12/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.12/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.12/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.12/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.12/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.12/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.12/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.12/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.12/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.12/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.12/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.12/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.12/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.12/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.12/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.12/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.12/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.12/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.12/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.12/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.12/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.12/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.12/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.12/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.12/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.12/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.12/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.12/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.12/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.12/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.12/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was created. */ post: operations["repository-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was deleted. */ post: operations["repository-ruleset/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was edited. */ post: operations["repository-ruleset/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.12/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.12/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.12/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.12/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.12/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.12/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.12/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.12/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.12/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.12/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.12/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.12/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.12/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was added to the enterprise. */ post: operations["user/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was removed from the enterprise. */ post: operations["user/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.12/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.12/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.12/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.12/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.12/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.12/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.12/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection configuration disabled event */ @@ -2589,8 +5555,8 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.12/admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.12/admin/overview/about-enterprise-accounts)." */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2619,8 +5585,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.12/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.12/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2631,7 +5597,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2653,7 +5619,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -2918,34 +5884,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -2983,34 +5949,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3348,9 +6314,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3358,7 +6324,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5412,10 +8379,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5449,16 +8416,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5468,7 +8435,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5482,14 +8449,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5499,7 +8466,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5523,8 +8490,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5542,37 +8509,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert auto-reopened event */ "webhook-dependabot-alert-auto-reopened": { /** @enum {string} */ @@ -6284,14 +9251,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -8065,7 +11029,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -9004,8 +11969,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9619,7 +12584,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -9813,11 +12778,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -9880,11 +12849,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -16961,7 +19930,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19124,7 +22093,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20678,19 +23647,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -21873,26 +24839,21 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -22292,17 +25253,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22369,7 +25330,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22377,9 +25338,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22389,8 +25350,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22639,17 +25600,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22716,7 +25677,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22724,9 +25685,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22736,8 +25697,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22960,9 +25921,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -22997,8 +25957,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -23048,9 +26008,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -23515,17 +26474,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23592,7 +26551,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23600,9 +26559,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23612,8 +26571,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23862,17 +26821,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23939,7 +26898,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23947,9 +26906,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23959,8 +26918,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24183,9 +27142,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24220,8 +27178,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24271,9 +27229,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -24737,17 +27694,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24814,7 +27771,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24822,9 +27779,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24834,8 +27791,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25081,17 +28038,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25158,7 +28115,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25166,9 +28123,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25178,8 +28135,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25402,9 +28359,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -25439,8 +28395,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -25490,9 +28446,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25632,31 +28587,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26033,17 +28988,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26110,7 +29065,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26118,17 +29073,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26377,17 +29332,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26454,7 +29409,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26462,17 +29417,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26695,9 +29650,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26732,8 +29686,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -26783,9 +29737,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27277,17 +30230,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27354,7 +30307,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27362,9 +30315,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27374,8 +30327,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27624,17 +30577,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27701,7 +30654,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27709,9 +30662,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27721,8 +30674,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27945,9 +30898,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27982,8 +30934,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -28033,9 +30985,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28498,17 +31449,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28575,7 +31526,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28583,9 +31534,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28595,8 +31546,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28845,17 +31796,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28922,7 +31873,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28930,9 +31881,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28942,8 +31893,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29166,9 +32117,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29203,8 +32153,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -29254,9 +32204,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29918,17 +32867,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29995,7 +32944,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30003,9 +32952,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30015,8 +32964,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30258,17 +33207,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30335,7 +33284,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30343,9 +33292,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30355,8 +33304,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30534,9 +33483,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30571,8 +33519,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -30622,9 +33570,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -31079,17 +34026,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31156,7 +34103,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31164,9 +34111,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31176,8 +34123,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31419,17 +34366,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31496,7 +34443,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31504,9 +34451,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31516,8 +34463,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31695,9 +34642,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31732,8 +34678,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -31783,9 +34729,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32395,17 +35340,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32472,7 +35417,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32480,9 +35425,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32492,8 +35437,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32735,17 +35680,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32812,7 +35757,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32820,9 +35765,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32832,8 +35777,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33011,9 +35956,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -33048,8 +35992,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -33099,9 +36043,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33556,17 +36499,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33633,7 +36576,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33641,9 +36584,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33653,8 +36596,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33896,17 +36839,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33973,7 +36916,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33981,9 +36924,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33993,8 +36936,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34172,9 +37115,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34209,8 +37151,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -34260,9 +37202,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34860,7 +37801,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35151,7 +38092,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35323,9 +38264,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35360,8 +38300,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -35411,9 +38351,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35602,9 +38541,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -35955,17 +38893,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36032,7 +38970,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36295,17 +39233,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36372,7 +39310,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36380,9 +39318,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36392,8 +39330,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36616,9 +39554,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36653,8 +39590,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -36704,9 +39641,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -36854,8 +39790,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -37206,17 +40142,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37283,7 +40219,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37291,9 +40227,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37303,8 +40239,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37553,17 +40489,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37630,7 +40566,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37638,9 +40574,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37650,8 +40586,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37874,9 +40810,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -37911,8 +40846,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37962,9 +40897,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38130,13 +41064,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -38487,17 +41418,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38564,7 +41495,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38572,9 +41503,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38584,8 +41515,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -38834,17 +41765,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38911,7 +41842,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38919,9 +41850,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38931,8 +41862,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39155,9 +42086,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39192,8 +42122,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39243,9 +42173,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39393,8 +42322,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -39745,17 +42674,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39822,7 +42751,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39830,9 +42759,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39842,8 +42771,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40092,17 +43021,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40169,7 +43098,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40177,9 +43106,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40189,8 +43118,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40413,9 +43342,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40450,8 +43378,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -40501,9 +43429,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40669,9 +43596,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -41021,17 +43946,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41098,7 +44023,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41106,9 +44031,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41118,8 +44043,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41361,17 +44286,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41438,7 +44363,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41446,9 +44371,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41458,8 +44383,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41637,9 +44562,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -41674,8 +44598,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -41725,9 +44649,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42243,7 +45166,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42541,7 +45464,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42715,9 +45638,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42752,8 +45674,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42803,9 +45725,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43473,7 +46394,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43771,7 +46692,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43945,9 +46866,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43982,8 +46902,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -44033,9 +46953,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44647,17 +47566,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44724,7 +47643,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44732,9 +47651,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44744,8 +47663,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45064,7 +47983,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45072,9 +47991,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45084,8 +48003,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45308,9 +48227,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45345,8 +48263,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45396,9 +48314,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45862,17 +48779,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -45939,7 +48856,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45947,9 +48864,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45959,8 +48876,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46209,17 +49126,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46286,7 +49203,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46294,9 +49211,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46306,8 +49223,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46530,9 +49447,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46567,8 +49483,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46618,9 +49534,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -47084,17 +49999,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -47161,7 +50076,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47169,9 +50084,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47181,8 +50096,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47501,7 +50416,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47509,9 +50424,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47521,8 +50436,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47745,9 +50660,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -47782,8 +50696,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -47833,9 +50747,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48298,17 +51211,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48375,7 +51288,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48383,9 +51296,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48395,8 +51308,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48645,17 +51558,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48722,7 +51635,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48730,9 +51643,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48742,8 +51655,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48966,9 +51879,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -49003,8 +51915,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -49054,9 +51966,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49512,7 +52423,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49635,19 +52546,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -49660,7 +52575,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -49672,21 +52588,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -50584,7 +53498,7 @@ export interface components { bypass_actors?: components["schemas"]["repository-ruleset-bypass-actor"][]; /** * @description The bypass type of the user making the API request for this ruleset. This field is only returned when - * querying the repository-level endpoint. + * querying the repository-level endpoint. * @enum {string} */ current_user_can_bypass?: "always" | "pull_requests_only" | "never"; @@ -50600,11 +53514,15 @@ export interface components { }; }; conditions?: - | null | ( - | components["schemas"]["repository-ruleset-conditions"] - | components["schemas"]["org-ruleset-conditions"] - ); + | null + | ( + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"] + ) + ) + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"]; rules?: components["schemas"]["repository-rule"][]; /** Format: date-time */ created_at?: string; @@ -50654,6 +53572,7 @@ export interface components { /** * Organization ruleset conditions * @description Conditions for an organization ruleset. The conditions object should contain both `repository_name` and `ref_name` properties or both `repository_id` and `ref_name` properties. + * */ "org-ruleset-conditions": | (components["schemas"]["repository-ruleset-conditions"] & @@ -51808,34 +54727,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52051,34 +54970,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52822,7 +55741,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53070,7 +55989,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53318,7 +56237,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53597,7 +56516,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53845,7 +56764,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -55647,22 +58566,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were disabled for a repository. - */ "branch-protection-configuration/disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55679,6 +58587,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55688,20 +58598,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were enabled for a repository. - */ "branch-protection-configuration/enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55718,6 +58624,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55727,18 +58635,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55759,6 +58665,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55768,18 +58676,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55800,6 +58706,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55809,18 +58717,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.12/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55841,6 +58747,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55850,13 +58758,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.12/admin/enterprise-management/caching-repositories/about-repository-caching)." */ "cache-sync": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55877,6 +58788,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55886,25 +58799,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55925,6 +58829,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55934,25 +58840,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55973,6 +58870,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55982,25 +58881,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.12/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56021,6 +58911,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56030,25 +58922,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.12/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56069,6 +58952,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56078,25 +58963,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.12/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56117,6 +58993,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56126,25 +59004,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.12/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.12/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.12/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56165,6 +59034,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56174,25 +59045,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.12/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.12/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.12/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.12/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56213,6 +59075,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56222,18 +59086,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56254,6 +59116,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56263,18 +59127,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56295,6 +59157,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56304,18 +59168,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56336,6 +59198,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56345,18 +59209,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56377,6 +59239,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56386,18 +59250,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56418,6 +59280,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56427,18 +59291,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.12/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.12/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56459,6 +59321,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56468,20 +59332,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.12/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56502,6 +59362,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56511,21 +59373,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56546,6 +59403,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56555,21 +59414,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56590,6 +59444,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56599,23 +59455,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. - */ "dependabot-alert/auto-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56636,6 +59485,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56645,23 +59496,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. - */ "dependabot-alert/auto-reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56682,6 +59526,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56691,23 +59537,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56728,6 +59567,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56737,23 +59578,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56774,6 +59608,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56783,23 +59619,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56820,6 +59649,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56829,23 +59660,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56866,6 +59690,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56875,23 +59701,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.12/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56912,6 +59731,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56921,18 +59742,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.12/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.12/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56953,6 +59772,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56962,18 +59783,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.12/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.12/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56994,6 +59813,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57003,20 +59824,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57037,6 +59854,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57046,18 +59865,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.12/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57078,6 +59895,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57087,20 +59906,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57121,6 +59936,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57130,20 +59947,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57164,6 +59977,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57173,20 +59988,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57207,6 +60018,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57216,23 +60029,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.12/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.12/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57253,6 +60059,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57262,23 +60070,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57299,6 +60100,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57308,23 +60111,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57345,6 +60141,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57354,23 +60152,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57391,6 +60182,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57400,23 +60193,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57437,6 +60223,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57446,23 +60234,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57483,6 +60264,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57492,23 +60275,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57529,6 +60305,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57538,23 +60316,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57575,6 +60346,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57584,23 +60357,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57621,6 +60387,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57630,23 +60398,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57667,6 +60428,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57676,23 +60439,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57713,6 +60469,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57722,23 +60480,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57759,6 +60510,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57768,23 +60521,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57805,6 +60551,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57814,23 +60562,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57851,6 +60592,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57860,23 +60603,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57897,6 +60633,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57906,23 +60644,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57943,6 +60674,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57952,23 +60685,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57989,6 +60715,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57998,23 +60726,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58035,6 +60756,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58044,23 +60767,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.12/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58081,6 +60797,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58090,16 +60808,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.12/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was disabled. - */ "enterprise/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58120,6 +60838,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58129,16 +60849,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.12/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was enabled. - */ "enterprise/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58159,6 +60879,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58168,17 +60890,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.12/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.12/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58199,6 +60920,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58208,20 +60931,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.12/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58242,6 +60961,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58251,17 +60972,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.12/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58282,6 +61002,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58291,18 +61013,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58323,6 +61043,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58332,18 +61054,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58364,6 +61084,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58373,18 +61095,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58405,6 +61125,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58414,18 +61136,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58446,6 +61166,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58455,18 +61177,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58487,6 +61207,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58496,18 +61218,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58528,6 +61248,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58537,16 +61259,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58567,6 +61289,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58576,18 +61300,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.12/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.12/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58608,6 +61330,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58617,20 +61341,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.12/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58651,6 +61371,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58660,20 +61382,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.12/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58694,6 +61412,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58703,20 +61423,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.12/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.12/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58737,6 +61453,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58746,20 +61464,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58780,6 +61494,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58789,20 +61505,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58823,6 +61535,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58832,20 +61546,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58866,6 +61576,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58875,20 +61587,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58909,6 +61617,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58918,20 +61628,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58952,6 +61658,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58961,20 +61669,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58995,6 +61699,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59004,20 +61710,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59038,6 +61740,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59047,20 +61751,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59081,6 +61781,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59090,20 +61792,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59124,6 +61822,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59133,20 +61833,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59167,6 +61863,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59176,20 +61874,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59210,6 +61904,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59219,20 +61915,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59253,6 +61945,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59262,20 +61956,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59296,6 +61986,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59305,20 +61997,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59339,6 +62027,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59348,20 +62038,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59382,6 +62068,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59391,20 +62079,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.12/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.12/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59425,6 +62109,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59434,20 +62120,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.12/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59468,6 +62150,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59477,20 +62161,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.12/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59511,6 +62191,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59520,20 +62202,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.12/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59554,6 +62232,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59563,18 +62243,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.12/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.12/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59595,6 +62273,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59604,18 +62284,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.12/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.12/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59636,6 +62314,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59645,18 +62325,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.12/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.12/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59677,6 +62355,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59686,18 +62366,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.12/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59718,6 +62396,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59727,18 +62407,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.12/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59759,6 +62437,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59768,18 +62448,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59800,6 +62478,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59809,20 +62489,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59843,6 +62519,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59852,20 +62530,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59886,6 +62560,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59895,20 +62571,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59929,6 +62601,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59938,20 +62612,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59972,6 +62642,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59981,20 +62653,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.12/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.12/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60015,6 +62683,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60024,20 +62694,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60058,6 +62724,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60067,20 +62735,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60101,6 +62765,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60110,20 +62776,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60144,6 +62806,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60153,20 +62817,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60187,6 +62847,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60196,20 +62858,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.12/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.12/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60230,6 +62888,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60239,18 +62899,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60271,6 +62929,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60280,18 +62940,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60312,6 +62970,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60321,17 +62981,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.12/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.12/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60352,6 +63011,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60361,21 +63022,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60392,6 +63048,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60401,21 +63059,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60432,6 +63085,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60441,21 +63096,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60472,6 +63122,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60481,21 +63133,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.12/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60512,6 +63159,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60521,13 +63170,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60548,6 +63200,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60557,22 +63211,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60593,6 +63241,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60602,22 +63252,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60638,6 +63282,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60647,22 +63293,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60683,6 +63323,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60692,22 +63334,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60728,6 +63364,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60737,22 +63375,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60773,6 +63405,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60782,22 +63416,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60818,6 +63446,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60827,22 +63457,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60863,6 +63487,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60872,22 +63498,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60908,6 +63528,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60917,22 +63539,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60953,6 +63569,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60962,22 +63580,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60998,6 +63610,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61007,22 +63621,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61043,6 +63651,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61052,22 +63662,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61088,6 +63692,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61097,22 +63703,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61133,6 +63733,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61142,22 +63744,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.12/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.12/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61178,6 +63774,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61187,23 +63785,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61224,6 +63815,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61233,23 +63826,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61270,6 +63856,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61279,23 +63867,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61316,6 +63897,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61325,23 +63908,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61362,6 +63938,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61371,23 +63949,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61408,6 +63979,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61417,23 +63990,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61454,6 +64020,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61463,23 +64031,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61500,6 +64061,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61509,23 +64072,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61546,6 +64102,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61555,23 +64113,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61592,6 +64143,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61601,23 +64154,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61638,6 +64184,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61647,23 +64195,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61684,6 +64225,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61693,23 +64236,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.12/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61730,6 +64266,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61739,17 +64277,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.12/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61770,6 +64307,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61779,20 +64318,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61813,6 +64348,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61822,20 +64359,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61856,6 +64389,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61865,20 +64400,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61899,6 +64430,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61908,20 +64441,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61942,6 +64471,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61951,20 +64482,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61985,6 +64512,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61994,20 +64523,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62028,6 +64553,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62037,20 +64564,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62071,6 +64594,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62080,20 +64605,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62114,6 +64635,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62123,20 +64646,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62157,6 +64676,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62166,20 +64687,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62200,6 +64717,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62209,20 +64728,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62243,6 +64758,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62252,20 +64769,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62286,6 +64799,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62295,20 +64810,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62329,6 +64840,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62338,20 +64851,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62372,6 +64881,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62381,20 +64892,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62415,6 +64922,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62424,20 +64933,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62458,6 +64963,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62467,20 +64974,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.12/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62501,6 +65004,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62510,20 +65015,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.12/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62544,6 +65045,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62553,20 +65056,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62587,6 +65086,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62596,20 +65097,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62630,6 +65127,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62639,20 +65138,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.12/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62673,6 +65168,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62682,20 +65179,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62716,6 +65209,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62725,20 +65220,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.12/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62759,6 +65250,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62768,20 +65261,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62802,6 +65291,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62811,20 +65302,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62845,6 +65332,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62854,20 +65343,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62888,6 +65373,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62897,20 +65384,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.12/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.12/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62931,6 +65414,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62940,22 +65425,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62976,6 +65455,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62985,21 +65466,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63020,6 +65496,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63029,21 +65507,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.12/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.12/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63064,6 +65537,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63073,18 +65548,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63105,6 +65578,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63114,18 +65589,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63146,6 +65619,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63155,18 +65630,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63187,6 +65660,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63196,18 +65671,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63228,6 +65701,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63237,18 +65712,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63269,6 +65742,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63278,18 +65753,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63310,6 +65783,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63319,18 +65794,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.12/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.12/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63351,6 +65824,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63360,18 +65835,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63392,6 +65865,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63401,18 +65876,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63433,6 +65906,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63442,18 +65917,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63474,6 +65947,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63483,18 +65958,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63515,6 +65988,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63524,18 +65999,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63556,6 +66029,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63565,17 +66040,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.12/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63596,6 +66070,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63605,18 +66081,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63637,6 +66111,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63646,18 +66122,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63678,6 +66152,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63687,18 +66163,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63719,6 +66193,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63728,18 +66204,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63760,6 +66234,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63769,20 +66245,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was created. - */ "repository-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63799,6 +66271,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63808,20 +66282,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was deleted. - */ "repository-ruleset/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63838,6 +66308,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63847,20 +66319,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.12/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.12/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.12/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was edited. - */ "repository-ruleset/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63877,6 +66345,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63886,18 +66356,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63918,6 +66386,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63927,18 +66397,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.12/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.12/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63959,6 +66427,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63968,19 +66438,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64001,6 +66468,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64010,19 +66479,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64043,6 +66509,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64052,19 +66520,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64085,6 +66550,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64094,19 +66561,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64127,6 +66591,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64136,20 +66602,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64170,6 +66632,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64179,22 +66643,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64215,6 +66673,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64224,20 +66684,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64258,6 +66714,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64267,20 +66725,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.12/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.12/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64301,6 +66755,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64310,18 +66766,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.12/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64342,6 +66796,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64351,18 +66807,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.12/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64383,6 +66837,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64392,18 +66848,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.12/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.12/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.12/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64424,6 +66878,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64433,17 +66889,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.12/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64464,6 +66919,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64473,20 +66930,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64507,6 +66960,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64516,18 +66971,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64548,6 +67001,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64557,18 +67012,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64589,6 +67042,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64598,20 +67053,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64632,6 +67083,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64641,18 +67094,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64673,6 +67124,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64682,18 +67135,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.12/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.12/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64714,6 +67165,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64723,18 +67176,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.12/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.12/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64755,6 +67206,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64764,18 +67217,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.12/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.12/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64796,6 +67247,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64805,17 +67258,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.12/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.12/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64836,6 +67288,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64845,20 +67299,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.12/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64879,6 +67329,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64888,19 +67340,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64921,6 +67370,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64930,19 +67381,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64963,6 +67411,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64972,19 +67422,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65005,6 +67452,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65014,19 +67463,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65047,6 +67493,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65056,19 +67504,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.12/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65089,6 +67534,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65098,16 +67545,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was added to the enterprise. - */ "user/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65128,6 +67575,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65137,16 +67586,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was removed from the enterprise. - */ "user/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65167,6 +67616,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65176,18 +67627,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.12/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.12/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65208,6 +67657,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65217,19 +67668,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.12/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65250,6 +67698,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65259,20 +67709,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65293,6 +67739,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65302,20 +67750,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65336,6 +67780,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65345,20 +67791,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65379,6 +67821,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65388,20 +67832,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.12/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65422,6 +67862,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65431,20 +67873,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.12/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65465,6 +67903,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65474,20 +67914,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.12/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65508,6 +67944,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65517,20 +67955,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.12/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.12/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.12/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65551,6 +67985,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65560,7 +67996,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types-ghes-3.13/types.d.ts b/packages/openapi-webhooks-types-ghes-3.13/types.d.ts index 5b214d2..fbab8c5 100644 --- a/packages/openapi-webhooks-types-ghes-3.13/types.d.ts +++ b/packages/openapi-webhooks-types-ghes-3.13/types.d.ts @@ -3,2588 +3,5567 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-configuration-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were disabled for a repository. */ post: operations["branch-protection-configuration/disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-configuration-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were enabled for a repository. */ post: operations["branch-protection-configuration/enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "cache-sync": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.13/admin/enterprise-management/caching-repositories/about-repository-caching)." */ post: operations["cache-sync"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.13/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.13/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.13/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.13/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.13/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.13/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.13/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.13/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.13/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. */ post: operations["dependabot-alert/auto-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. */ post: operations["dependabot-alert/auto-reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.13/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.13/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.13/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.13/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.13/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.13/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was disabled. */ post: operations["enterprise/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.13/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was enabled. */ post: operations["enterprise/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.13/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.13/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.13/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.13/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.13/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.13/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.13/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.13/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.13/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.13/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.13/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.13/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.13/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.13/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.13/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.13/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.13/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.13/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.13/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.13/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.13/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.13/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.13/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.13/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.13/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.13/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.13/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.13/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.13/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.13/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.13/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.13/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.13/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was created. */ post: operations["repository-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was deleted. */ post: operations["repository-ruleset/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was edited. */ post: operations["repository-ruleset/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-validated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was validated. */ post: operations["secret-scanning-alert/validated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.13/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.13/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.13/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.13/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.13/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.13/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.13/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.13/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.13/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.13/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.13/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.13/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.13/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was added to the enterprise. */ post: operations["user/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was removed from the enterprise. */ post: operations["user/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.13/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.13/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.13/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.13/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.13/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.13/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.13/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection configuration disabled event */ @@ -2600,8 +5579,8 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.13/admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.13/admin/overview/about-enterprise-accounts)." */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2630,8 +5609,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.13/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.13/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2642,7 +5621,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2664,7 +5643,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -2933,34 +5912,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -2998,34 +5977,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3363,9 +6342,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3373,7 +6352,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5427,10 +8407,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5464,16 +8444,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5483,7 +8463,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5497,14 +8477,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5514,7 +8494,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5538,8 +8518,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5557,37 +8537,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert auto-reopened event */ "webhook-dependabot-alert-auto-reopened": { /** @enum {string} */ @@ -6299,14 +9279,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -8080,7 +11057,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -9019,8 +11997,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9634,7 +12612,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -9828,11 +12806,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -9895,11 +12877,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -16985,7 +19967,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19152,7 +22134,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20706,19 +23688,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -21901,26 +24880,21 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -22320,17 +25294,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22397,7 +25371,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22405,9 +25379,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22417,8 +25391,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22667,17 +25641,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22744,7 +25718,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22752,9 +25726,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22764,8 +25738,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22988,9 +25962,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -23025,8 +25998,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -23076,9 +26049,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -23543,17 +26515,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23620,7 +26592,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23628,9 +26600,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23640,8 +26612,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23890,17 +26862,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23967,7 +26939,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23975,9 +26947,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23987,8 +26959,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24211,9 +27183,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24248,8 +27219,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24299,9 +27270,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -24765,17 +27735,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24842,7 +27812,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24850,9 +27820,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24862,8 +27832,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25109,17 +28079,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25186,7 +28156,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25194,9 +28164,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25206,8 +28176,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25430,9 +28400,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -25467,8 +28436,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -25518,9 +28487,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25660,31 +28628,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26061,17 +29029,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26138,7 +29106,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26146,17 +29114,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26405,17 +29373,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26482,7 +29450,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26490,17 +29458,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26723,9 +29691,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26760,8 +29727,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -26811,9 +29778,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27305,17 +30271,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27382,7 +30348,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27390,9 +30356,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27402,8 +30368,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27652,17 +30618,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27729,7 +30695,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27737,9 +30703,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27749,8 +30715,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27973,9 +30939,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -28010,8 +30975,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -28061,9 +31026,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28526,17 +31490,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28603,7 +31567,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28611,9 +31575,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28623,8 +31587,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28873,17 +31837,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28950,7 +31914,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28958,9 +31922,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28970,8 +31934,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29194,9 +32158,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29231,8 +32194,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -29282,9 +32245,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29946,17 +32908,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30023,7 +32985,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30031,9 +32993,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30043,8 +33005,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30286,17 +33248,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30363,7 +33325,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30371,9 +33333,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30383,8 +33345,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30562,9 +33524,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30599,8 +33560,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -30650,9 +33611,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -31107,17 +34067,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31184,7 +34144,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31192,9 +34152,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31204,8 +34164,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31447,17 +34407,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31524,7 +34484,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31532,9 +34492,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31544,8 +34504,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31723,9 +34683,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31760,8 +34719,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -31811,9 +34770,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32423,17 +35381,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32500,7 +35458,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32508,9 +35466,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32520,8 +35478,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32763,17 +35721,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32840,7 +35798,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32848,9 +35806,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32860,8 +35818,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33039,9 +35997,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -33076,8 +36033,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -33127,9 +36084,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33584,17 +36540,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33661,7 +36617,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33669,9 +36625,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33681,8 +36637,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33924,17 +36880,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -34001,7 +36957,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -34009,9 +36965,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -34021,8 +36977,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34200,9 +37156,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34237,8 +37192,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -34288,9 +37243,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34888,7 +37842,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35179,7 +38133,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35351,9 +38305,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35388,8 +38341,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -35439,9 +38392,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35630,9 +38582,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -35983,17 +38934,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36060,7 +39011,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36323,17 +39274,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36400,7 +39351,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36408,9 +39359,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36420,8 +39371,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36644,9 +39595,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36681,8 +39631,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -36732,9 +39682,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -36882,8 +39831,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -37234,17 +40183,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37311,7 +40260,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37319,9 +40268,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37331,8 +40280,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37581,17 +40530,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37658,7 +40607,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37666,9 +40615,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37678,8 +40627,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37902,9 +40851,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -37939,8 +40887,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37990,9 +40938,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38158,13 +41105,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -38515,17 +41459,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38592,7 +41536,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38600,9 +41544,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38612,8 +41556,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -38862,17 +41806,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38939,7 +41883,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38947,9 +41891,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38959,8 +41903,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39183,9 +42127,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39220,8 +42163,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39271,9 +42214,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39421,8 +42363,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -39773,17 +42715,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39850,7 +42792,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39858,9 +42800,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39870,8 +42812,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40120,17 +43062,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40197,7 +43139,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40205,9 +43147,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40217,8 +43159,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40441,9 +43383,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40478,8 +43419,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -40529,9 +43470,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40697,9 +43637,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -41049,17 +43987,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41126,7 +44064,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41134,9 +44072,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41146,8 +44084,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41389,17 +44327,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41466,7 +44404,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41474,9 +44412,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41486,8 +44424,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41665,9 +44603,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -41702,8 +44639,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -41753,9 +44690,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42271,7 +45207,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42569,7 +45505,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42743,9 +45679,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42780,8 +45715,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42831,9 +45766,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43501,7 +46435,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43799,7 +46733,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43973,9 +46907,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -44010,8 +46943,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -44061,9 +46994,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44675,17 +47607,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44752,7 +47684,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44760,9 +47692,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44772,8 +47704,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45092,7 +48024,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45100,9 +48032,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45112,8 +48044,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45336,9 +48268,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45373,8 +48304,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45424,9 +48355,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45890,17 +48820,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -45967,7 +48897,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45975,9 +48905,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45987,8 +48917,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46237,17 +49167,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46314,7 +49244,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46322,9 +49252,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46334,8 +49264,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46558,9 +49488,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46595,8 +49524,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46646,9 +49575,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -47112,17 +50040,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -47189,7 +50117,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47197,9 +50125,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47209,8 +50137,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47529,7 +50457,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47537,9 +50465,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47549,8 +50477,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47773,9 +50701,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -47810,8 +50737,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -47861,9 +50788,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48326,17 +51252,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48403,7 +51329,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48411,9 +51337,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48423,8 +51349,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48673,17 +51599,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48750,7 +51676,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48758,9 +51684,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48770,8 +51696,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48994,9 +51920,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -49031,8 +51956,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -49082,9 +52007,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49544,7 +52468,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49667,19 +52591,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -49692,7 +52620,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -49704,21 +52633,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -50602,8 +53529,8 @@ export interface components { /** * @description The target of the ruleset * - * > [!NOTE] - * > The `push` target is in beta and is subject to change. + * > [!NOTE] + * > The `push` target is in beta and is subject to change. * @enum {string} */ target?: "branch" | "tag" | "push"; @@ -50619,7 +53546,7 @@ export interface components { bypass_actors?: components["schemas"]["repository-ruleset-bypass-actor"][]; /** * @description The bypass type of the user making the API request for this ruleset. This field is only returned when - * querying the repository-level endpoint. + * querying the repository-level endpoint. * @enum {string} */ current_user_can_bypass?: "always" | "pull_requests_only" | "never"; @@ -50635,11 +53562,15 @@ export interface components { }; }; conditions?: - | null | ( - | components["schemas"]["repository-ruleset-conditions"] - | components["schemas"]["org-ruleset-conditions"] - ); + | null + | ( + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"] + ) + ) + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"]; rules?: components["schemas"]["repository-rule"][]; /** Format: date-time */ created_at?: string; @@ -50689,6 +53620,7 @@ export interface components { /** * Organization ruleset conditions * @description Conditions for an organization ruleset. The conditions object should contain both `repository_name` and `ref_name` properties or both `repository_id` and `ref_name` properties. + * */ "org-ruleset-conditions": | (components["schemas"]["repository-ruleset-conditions"] & @@ -51883,34 +54815,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52126,34 +55058,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52901,7 +55833,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53153,7 +56085,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53405,7 +56337,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53688,7 +56620,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53940,7 +56872,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -55742,22 +58674,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were disabled for a repository. - */ "branch-protection-configuration/disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55774,6 +58695,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55783,20 +58706,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were enabled for a repository. - */ "branch-protection-configuration/enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55813,6 +58732,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55822,18 +58743,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55854,6 +58773,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55863,18 +58784,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55895,6 +58814,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55904,18 +58825,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.13/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55936,6 +58855,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55945,13 +58866,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.13/admin/enterprise-management/caching-repositories/about-repository-caching)." */ "cache-sync": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -55972,6 +58896,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -55981,25 +58907,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56020,6 +58937,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56029,25 +58948,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56068,6 +58978,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56077,25 +58989,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.13/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56116,6 +59019,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56125,25 +59030,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.13/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56164,6 +59060,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56173,25 +59071,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.13/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56212,6 +59101,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56221,25 +59112,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.13/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.13/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.13/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56260,6 +59142,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56269,25 +59153,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.13/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.13/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.13/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.13/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56308,6 +59183,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56317,18 +59194,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56349,6 +59224,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56358,18 +59235,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56390,6 +59265,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56399,18 +59276,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56431,6 +59306,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56440,18 +59317,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56472,6 +59347,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56481,18 +59358,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56513,6 +59388,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56522,18 +59399,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.13/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.13/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56554,6 +59429,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56563,20 +59440,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.13/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56597,6 +59470,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56606,21 +59481,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56641,6 +59511,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56650,21 +59522,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56685,6 +59552,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56694,23 +59563,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. - */ "dependabot-alert/auto-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56731,6 +59593,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56740,23 +59604,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. - */ "dependabot-alert/auto-reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56777,6 +59634,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56786,23 +59645,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56823,6 +59675,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56832,23 +59686,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56869,6 +59716,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56878,23 +59727,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56915,6 +59757,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56924,23 +59768,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56961,6 +59798,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56970,23 +59809,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.13/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57007,6 +59839,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57016,18 +59850,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.13/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.13/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57048,6 +59880,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57057,18 +59891,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.13/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.13/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57089,6 +59921,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57098,20 +59932,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57132,6 +59962,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57141,18 +59973,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.13/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57173,6 +60003,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57182,20 +60014,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57216,6 +60044,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57225,20 +60055,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57259,6 +60085,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57268,20 +60096,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57302,6 +60126,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57311,23 +60137,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.13/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.13/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57348,6 +60167,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57357,23 +60178,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57394,6 +60208,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57403,23 +60219,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57440,6 +60249,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57449,23 +60260,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57486,6 +60290,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57495,23 +60301,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57532,6 +60331,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57541,23 +60342,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57578,6 +60372,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57587,23 +60383,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57624,6 +60413,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57633,23 +60424,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57670,6 +60454,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57679,23 +60465,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57716,6 +60495,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57725,23 +60506,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57762,6 +60536,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57771,23 +60547,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57808,6 +60577,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57817,23 +60588,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57854,6 +60618,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57863,23 +60629,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57900,6 +60659,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57909,23 +60670,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57946,6 +60700,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57955,23 +60711,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57992,6 +60741,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58001,23 +60752,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58038,6 +60782,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58047,23 +60793,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58084,6 +60823,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58093,23 +60834,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58130,6 +60864,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58139,23 +60875,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.13/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58176,6 +60905,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58185,16 +60916,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.13/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was disabled. - */ "enterprise/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58215,6 +60946,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58224,16 +60957,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.13/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was enabled. - */ "enterprise/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58254,6 +60987,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58263,17 +60998,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.13/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.13/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58294,6 +61028,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58303,20 +61039,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.13/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58337,6 +61069,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58346,17 +61080,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.13/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58377,6 +61110,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58386,18 +61121,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58418,6 +61151,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58427,18 +61162,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58459,6 +61192,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58468,18 +61203,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58500,6 +61233,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58509,18 +61244,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58541,6 +61274,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58550,18 +61285,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58582,6 +61315,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58591,18 +61326,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58623,6 +61356,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58632,16 +61367,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58662,6 +61397,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58671,18 +61408,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.13/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.13/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58703,6 +61438,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58712,20 +61449,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.13/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58746,6 +61479,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58755,20 +61490,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.13/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58789,6 +61520,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58798,20 +61531,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.13/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.13/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58832,6 +61561,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58841,20 +61572,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58875,6 +61602,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58884,20 +61613,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58918,6 +61643,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58927,20 +61654,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58961,6 +61684,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58970,20 +61695,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59004,6 +61725,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59013,20 +61736,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59047,6 +61766,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59056,20 +61777,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59090,6 +61807,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59099,20 +61818,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59133,6 +61848,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59142,20 +61859,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59176,6 +61889,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59185,20 +61900,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59219,6 +61930,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59228,20 +61941,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59262,6 +61971,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59271,20 +61982,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59305,6 +62012,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59314,20 +62023,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59348,6 +62053,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59357,20 +62064,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59391,6 +62094,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59400,20 +62105,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59434,6 +62135,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59443,20 +62146,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59477,6 +62176,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59486,20 +62187,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.13/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.13/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59520,6 +62217,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59529,20 +62228,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.13/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59563,6 +62258,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59572,20 +62269,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.13/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59606,6 +62299,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59615,20 +62310,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.13/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59649,6 +62340,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59658,18 +62351,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.13/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.13/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59690,6 +62381,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59699,18 +62392,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.13/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.13/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59731,6 +62422,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59740,18 +62433,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.13/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.13/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59772,6 +62463,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59781,18 +62474,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.13/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59813,6 +62504,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59822,18 +62515,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.13/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59854,6 +62545,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59863,18 +62556,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59895,6 +62586,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59904,20 +62597,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59938,6 +62627,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59947,20 +62638,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59981,6 +62668,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59990,20 +62679,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60024,6 +62709,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60033,20 +62720,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60067,6 +62750,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60076,20 +62761,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.13/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.13/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60110,6 +62791,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60119,20 +62802,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60153,6 +62832,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60162,20 +62843,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60196,6 +62873,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60205,20 +62884,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60239,6 +62914,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60248,20 +62925,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60282,6 +62955,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60291,20 +62966,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.13/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.13/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60325,6 +62996,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60334,18 +63007,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60366,6 +63037,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60375,18 +63048,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60407,6 +63078,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60416,17 +63089,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.13/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.13/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60447,6 +63119,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60456,21 +63130,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60487,6 +63156,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60496,21 +63167,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60527,6 +63193,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60536,21 +63204,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60567,6 +63230,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60576,21 +63241,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.13/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60607,6 +63267,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60616,13 +63278,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60643,6 +63308,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60652,22 +63319,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60688,6 +63349,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60697,22 +63360,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60733,6 +63390,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60742,22 +63401,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60778,6 +63431,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60787,22 +63442,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60823,6 +63472,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60832,22 +63483,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60868,6 +63513,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60877,22 +63524,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60913,6 +63554,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60922,22 +63565,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60958,6 +63595,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60967,22 +63606,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61003,6 +63636,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61012,22 +63647,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61048,6 +63677,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61057,22 +63688,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61093,6 +63718,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61102,22 +63729,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61138,6 +63759,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61147,22 +63770,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61183,6 +63800,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61192,22 +63811,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61228,6 +63841,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61237,22 +63852,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.13/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.13/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61273,6 +63882,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61282,23 +63893,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61319,6 +63923,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61328,23 +63934,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61365,6 +63964,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61374,23 +63975,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61411,6 +64005,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61420,23 +64016,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61457,6 +64046,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61466,23 +64057,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61503,6 +64087,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61512,23 +64098,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61549,6 +64128,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61558,23 +64139,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61595,6 +64169,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61604,23 +64180,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61641,6 +64210,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61650,23 +64221,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61687,6 +64251,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61696,23 +64262,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61733,6 +64292,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61742,23 +64303,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61779,6 +64333,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61788,23 +64344,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.13/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61825,6 +64374,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61834,17 +64385,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.13/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61865,6 +64415,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61874,20 +64426,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61908,6 +64456,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61917,20 +64467,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61951,6 +64497,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61960,20 +64508,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61994,6 +64538,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62003,20 +64549,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62037,6 +64579,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62046,20 +64590,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62080,6 +64620,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62089,20 +64631,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62123,6 +64661,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62132,20 +64672,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62166,6 +64702,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62175,20 +64713,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62209,6 +64743,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62218,20 +64754,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62252,6 +64784,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62261,20 +64795,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62295,6 +64825,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62304,20 +64836,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62338,6 +64866,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62347,20 +64877,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62381,6 +64907,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62390,20 +64918,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62424,6 +64948,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62433,20 +64959,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62467,6 +64989,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62476,20 +65000,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62510,6 +65030,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62519,20 +65041,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62553,6 +65071,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62562,20 +65082,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.13/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62596,6 +65112,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62605,20 +65123,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.13/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62639,6 +65153,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62648,20 +65164,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62682,6 +65194,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62691,20 +65205,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62725,6 +65235,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62734,20 +65246,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.13/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62768,6 +65276,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62777,20 +65287,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62811,6 +65317,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62820,20 +65328,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.13/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62854,6 +65358,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62863,20 +65369,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62897,6 +65399,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62906,20 +65410,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62940,6 +65440,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62949,20 +65451,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62983,6 +65481,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62992,20 +65492,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.13/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.13/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63026,6 +65522,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63035,22 +65533,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63071,6 +65563,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63080,21 +65574,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63115,6 +65604,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63124,21 +65615,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.13/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.13/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63159,6 +65645,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63168,18 +65656,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63200,6 +65686,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63209,18 +65697,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63241,6 +65727,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63250,18 +65738,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63282,6 +65768,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63291,18 +65779,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63323,6 +65809,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63332,18 +65820,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63364,6 +65850,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63373,18 +65861,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63405,6 +65891,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63414,18 +65902,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.13/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.13/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63446,6 +65932,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63455,18 +65943,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63487,6 +65973,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63496,18 +65984,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63528,6 +66014,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63537,18 +66025,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63569,6 +66055,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63578,18 +66066,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63610,6 +66096,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63619,18 +66107,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63651,6 +66137,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63660,17 +66148,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.13/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63691,6 +66178,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63700,18 +66189,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63732,6 +66219,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63741,18 +66230,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63773,6 +66260,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63782,18 +66271,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63814,6 +66301,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63823,18 +66312,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63855,6 +66342,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63864,20 +66353,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was created. - */ "repository-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63894,6 +66379,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63903,20 +66390,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was deleted. - */ "repository-ruleset/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63933,6 +66416,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63942,20 +66427,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.13/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.13/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.13/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was edited. - */ "repository-ruleset/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63972,6 +66453,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63981,18 +66464,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64013,6 +66494,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64022,18 +66505,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.13/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.13/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64054,6 +66535,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64063,19 +66546,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64096,6 +66576,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64105,19 +66587,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64138,6 +66617,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64147,19 +66628,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64180,6 +66658,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64189,19 +66669,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64222,6 +66699,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64231,20 +66710,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64265,6 +66740,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64274,22 +66751,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64310,6 +66781,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64319,20 +66792,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64353,6 +66822,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64362,20 +66833,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64396,6 +66863,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64405,20 +66874,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.13/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.13/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was validated. - */ "secret-scanning-alert/validated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64439,6 +66904,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64448,18 +66915,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.13/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64480,6 +66945,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64489,18 +66956,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.13/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64521,6 +66986,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64530,18 +66997,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.13/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.13/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.13/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64562,6 +67027,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64571,17 +67038,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.13/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64602,6 +67068,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64611,20 +67079,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64645,6 +67109,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64654,18 +67120,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64686,6 +67150,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64695,18 +67161,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64727,6 +67191,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64736,20 +67202,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64770,6 +67232,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64779,18 +67243,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64811,6 +67273,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64820,18 +67284,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.13/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.13/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64852,6 +67314,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64861,18 +67325,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.13/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.13/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64893,6 +67355,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64902,18 +67366,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.13/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.13/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64934,6 +67396,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64943,17 +67407,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.13/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.13/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64974,6 +67437,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64983,20 +67448,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.13/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65017,6 +67478,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65026,19 +67489,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65059,6 +67519,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65068,19 +67530,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65101,6 +67560,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65110,19 +67571,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65143,6 +67601,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65152,19 +67612,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65185,6 +67642,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65194,19 +67653,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.13/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65227,6 +67683,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65236,16 +67694,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was added to the enterprise. - */ "user/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65266,6 +67724,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65275,16 +67735,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was removed from the enterprise. - */ "user/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65305,6 +67765,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65314,18 +67776,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.13/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.13/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65346,6 +67806,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65355,19 +67817,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.13/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65388,6 +67847,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65397,20 +67858,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65431,6 +67888,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65440,20 +67899,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65474,6 +67929,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65483,20 +67940,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65517,6 +67970,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65526,20 +67981,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.13/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65560,6 +68011,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65569,20 +68022,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.13/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65603,6 +68052,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65612,20 +68063,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.13/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65646,6 +68093,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65655,20 +68104,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.13/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.13/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.13/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65689,6 +68134,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65698,7 +68145,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types-ghes-3.14/types.d.ts b/packages/openapi-webhooks-types-ghes-3.14/types.d.ts index 67a6745..70db3a3 100644 --- a/packages/openapi-webhooks-types-ghes-3.14/types.d.ts +++ b/packages/openapi-webhooks-types-ghes-3.14/types.d.ts @@ -3,2653 +3,5697 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-configuration-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were disabled for a repository. */ post: operations["branch-protection-configuration/disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-configuration-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were enabled for a repository. */ post: operations["branch-protection-configuration/enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning push protection bypass request was cancelled. */ post: operations["exemption-request-secret-scanning/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning bypass request was completed. */ post: operations["exemption-request-secret-scanning/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning push protection bypass request was created. */ post: operations["exemption-request-secret-scanning/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-response-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A secret scanning push protection bypass response was dismissed. */ post: operations["exemption-request-secret-scanning/response-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "bypass-request-secret-scanning-response-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." + * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * - * Note: Delegated bypass for push protection is currently in beta and subject to change. + * Note: Delegated bypass for push protection is currently in beta and subject to change. * @description A response either approving or rejecting the secret scanning push protection bypass request was submitted. */ post: operations["exemption-request-secret-scanning/response-submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "cache-sync": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.14/admin/enterprise-management/caching-repositories/about-repository-caching)." */ post: operations["cache-sync"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.14/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.14/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.14/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.14/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.14/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.14/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.14/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.14/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.14/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. */ post: operations["dependabot-alert/auto-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. */ post: operations["dependabot-alert/auto-reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.14/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.14/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.14/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.14/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.14/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.14/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was disabled. */ post: operations["enterprise/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "enterprise-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.14/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." * @description Anonymous Git read access was enabled. */ post: operations["enterprise/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.14/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.14/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.14/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.14/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.14/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.14/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.14/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.14/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.14/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.14/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.14/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.14/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.14/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.14/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.14/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.14/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.14/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.14/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.14/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.14/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.14/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.14/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.14/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.14/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.14/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.14/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.14/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.14/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.14/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.14/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.14/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.14/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.14/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was created. */ post: operations["repository-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was deleted. */ post: operations["repository-ruleset/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was edited. */ post: operations["repository-ruleset/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-validated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was validated. */ post: operations["secret-scanning-alert/validated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.14/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.14/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.14/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.14/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.14/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.14/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.14/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.14/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.14/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.14/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.14/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.14/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.14/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was added to the enterprise. */ post: operations["user/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was removed from the enterprise. */ post: operations["user/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.14/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.14/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.14/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.14/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.14/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.14/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.14/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection configuration disabled event */ @@ -2665,8 +5709,8 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.14/admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/enterprise-server@3.14/admin/overview/about-enterprise-accounts)." */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2695,8 +5739,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.14/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/enterprise-server@3.14/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2707,7 +5751,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2729,7 +5773,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -2998,34 +6042,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3063,34 +6107,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3373,10 +6417,8 @@ export interface components { /** @description The comment the requester provided when creating the exemption request. */ requester_comment?: string | null; /** @description Metadata about the exemption request. */ - metadata?: - | components["schemas"]["exemption-request-secret-scanning-metadata"] - | Record - | null; + metadata?: (Record | null) & + components["schemas"]["exemption-request-secret-scanning-metadata"]; /** * Format: date-time * @description The date and time the exemption request will expire. @@ -3615,9 +6657,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3625,7 +6667,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5679,10 +8722,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5716,16 +8759,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5735,7 +8778,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5749,14 +8792,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5766,7 +8809,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5790,8 +8833,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5809,37 +8852,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert auto-reopened event */ "webhook-dependabot-alert-auto-reopened": { /** @enum {string} */ @@ -6551,14 +9594,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -8332,7 +11372,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -9271,8 +12312,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9886,7 +12927,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -10080,11 +13121,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -10147,11 +13192,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -17237,7 +20282,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19404,7 +22449,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20057,12 +23102,10 @@ export interface components { /** @enum {string} */ action: "added"; changes?: { - /** - * @description This field is included for legacy purposes; use the `role_name` field instead. The `maintain` - * role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role - * assigned to the collaborator, use the `role_name` field instead, which will provide the full - * role name, including custom roles. - */ + /** @description This field is included for legacy purposes; use the `role_name` field instead. The `maintain` + * role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role + * assigned to the collaborator, use the `role_name` field instead, which will provide the full + * role name, including custom roles. */ permission?: { /** @enum {string} */ to: "write" | "admin" | "read"; @@ -20968,19 +24011,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -22163,42 +25203,37 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes altered values for text, number, date, single select, and iteration fields, along with the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes altered values for text, number, date, single select, and iteration fields, along with the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; field_name?: string; project_number?: number; - from?: - | string - | number - | components["schemas"]["projects-v2-single-select-option"] - | components["schemas"]["projects-v2-iteration-setting"] - | null - | Record; - to?: - | string - | number - | components["schemas"]["projects-v2-single-select-option"] - | components["schemas"]["projects-v2-iteration-setting"] - | null - | Record; + from?: (null | Record) & + ( + | string + | number + | components["schemas"]["projects-v2-single-select-option"] + | components["schemas"]["projects-v2-iteration-setting"] + ); + to?: (null | Record) & + ( + | string + | number + | components["schemas"]["projects-v2-single-select-option"] + | components["schemas"]["projects-v2-iteration-setting"] + ); }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -22618,17 +25653,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22695,7 +25730,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22703,9 +25738,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22715,8 +25750,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -22965,17 +26000,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23042,7 +26077,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23050,9 +26085,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23062,8 +26097,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23286,9 +26321,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -23323,8 +26357,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -23374,9 +26408,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -23841,17 +26874,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23918,7 +26951,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23926,9 +26959,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23938,8 +26971,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24188,17 +27221,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24265,7 +27298,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24273,9 +27306,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24285,8 +27318,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24509,9 +27542,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24546,8 +27578,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24597,9 +27629,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25063,17 +28094,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25140,7 +28171,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25148,9 +28179,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25160,8 +28191,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25407,17 +28438,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25484,7 +28515,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25492,9 +28523,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25504,8 +28535,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25728,9 +28759,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -25765,8 +28795,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -25816,9 +28846,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25958,31 +28987,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26359,17 +29388,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26436,7 +29465,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26444,17 +29473,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26703,17 +29732,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26780,7 +29809,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26788,17 +29817,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27021,9 +30050,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27058,8 +30086,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -27109,9 +30137,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27603,17 +30630,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27680,7 +30707,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27688,9 +30715,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27700,8 +30727,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27950,17 +30977,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28027,7 +31054,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28035,9 +31062,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28047,8 +31074,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28271,9 +31298,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -28308,8 +31334,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -28359,9 +31385,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28824,17 +31849,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28901,7 +31926,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28909,9 +31934,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28921,8 +31946,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29171,17 +32196,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29248,7 +32273,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29256,9 +32281,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29268,8 +32293,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29492,9 +32517,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29529,8 +32553,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -29580,9 +32604,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -30244,17 +33267,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30321,7 +33344,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30329,9 +33352,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30341,8 +33364,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30584,17 +33607,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30661,7 +33684,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30669,9 +33692,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30681,8 +33704,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30860,9 +33883,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30897,8 +33919,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -30948,9 +33970,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -31405,17 +34426,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31482,7 +34503,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31490,9 +34511,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31502,8 +34523,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31745,17 +34766,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31822,7 +34843,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31830,9 +34851,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31842,8 +34863,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32021,9 +35042,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -32058,8 +35078,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -32109,9 +35129,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32721,17 +35740,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32798,7 +35817,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32806,9 +35825,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32818,8 +35837,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33061,17 +36080,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33138,7 +36157,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33146,9 +36165,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33158,8 +36177,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33337,9 +36356,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -33374,8 +36392,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -33425,9 +36443,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33882,17 +36899,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33959,7 +36976,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33967,9 +36984,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33979,8 +36996,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34222,17 +37239,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -34299,7 +37316,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -34307,9 +37324,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -34319,8 +37336,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34498,9 +37515,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34535,8 +37551,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -34586,9 +37602,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35186,7 +38201,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35477,7 +38492,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35649,9 +38664,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35686,8 +38700,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -35737,9 +38751,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35928,9 +38941,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -36281,17 +39293,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36358,7 +39370,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36621,17 +39633,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36698,7 +39710,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36706,9 +39718,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36718,8 +39730,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36942,9 +39954,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36979,8 +39990,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37030,9 +40041,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -37180,8 +40190,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -37532,17 +40542,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37609,7 +40619,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37617,9 +40627,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37629,8 +40639,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37879,17 +40889,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37956,7 +40966,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37964,9 +40974,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37976,8 +40986,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -38200,9 +41210,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -38237,8 +41246,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -38288,9 +41297,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38456,13 +41464,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -38813,17 +41818,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38890,7 +41895,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38898,9 +41903,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38910,8 +41915,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39160,17 +42165,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39237,7 +42242,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39245,9 +42250,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39257,8 +42262,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39481,9 +42486,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39518,8 +42522,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39569,9 +42573,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39719,8 +42722,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -40071,17 +43074,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40148,7 +43151,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40156,9 +43159,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40168,8 +43171,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40418,17 +43421,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40495,7 +43498,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40503,9 +43506,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40515,8 +43518,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40739,9 +43742,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40776,8 +43778,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -40827,9 +43829,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40995,9 +43996,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -41347,17 +44346,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41424,7 +44423,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41432,9 +44431,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41444,8 +44443,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41687,17 +44686,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41764,7 +44763,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41772,9 +44771,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41784,8 +44783,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41963,9 +44962,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42000,8 +44998,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42051,9 +45049,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42569,7 +45566,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42867,7 +45864,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43041,9 +46038,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43078,8 +46074,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -43129,9 +46125,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43799,7 +46794,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44097,7 +47092,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44271,9 +47266,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -44308,8 +47302,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -44359,9 +47353,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44973,17 +47966,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -45050,7 +48043,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45058,9 +48051,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45070,8 +48063,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45390,7 +48383,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45398,9 +48391,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45410,8 +48403,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45634,9 +48627,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45671,8 +48663,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45722,9 +48714,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -46188,17 +49179,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46265,7 +49256,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46273,9 +49264,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46285,8 +49276,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46535,17 +49526,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46612,7 +49603,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46620,9 +49611,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46632,8 +49623,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46856,9 +49847,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46893,8 +49883,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46944,9 +49934,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -47410,17 +50399,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -47487,7 +50476,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47495,9 +50484,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47507,8 +50496,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -47827,7 +50816,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47835,9 +50824,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47847,8 +50836,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48071,9 +51060,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -48108,8 +51096,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -48159,9 +51147,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48624,17 +51611,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48701,7 +51688,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48709,9 +51696,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48721,8 +51708,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48971,17 +51958,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -49048,7 +52035,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49056,9 +52043,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -49068,8 +52055,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -49292,9 +52279,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -49329,8 +52315,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -49380,9 +52366,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49842,7 +52827,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49965,19 +52950,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -49990,7 +52979,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -50002,21 +52992,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -50900,8 +53888,8 @@ export interface components { /** * @description The target of the ruleset * - * > [!NOTE] - * > The `push` target is in beta and is subject to change. + * > [!NOTE] + * > The `push` target is in beta and is subject to change. * @enum {string} */ target?: "branch" | "tag" | "push"; @@ -50917,7 +53905,7 @@ export interface components { bypass_actors?: components["schemas"]["repository-ruleset-bypass-actor"][]; /** * @description The bypass type of the user making the API request for this ruleset. This field is only returned when - * querying the repository-level endpoint. + * querying the repository-level endpoint. * @enum {string} */ current_user_can_bypass?: "always" | "pull_requests_only" | "never"; @@ -50933,11 +53921,15 @@ export interface components { }; }; conditions?: - | null | ( - | components["schemas"]["repository-ruleset-conditions"] - | components["schemas"]["org-ruleset-conditions"] - ); + | null + | ( + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"] + ) + ) + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"]; rules?: components["schemas"]["repository-rule"][]; /** Format: date-time */ created_at?: string; @@ -50954,7 +53946,8 @@ export interface components { * @description An actor that can bypass rules in a ruleset */ "repository-ruleset-bypass-actor": { - /** @description The ID of the actor that can bypass a ruleset. If `actor_type` is `OrganizationAdmin`, this should be `1`. If `actor_type` is `DeployKey`, this should be null. `OrganizationAdmin` is not applicable for personal repositories. */ + /** @description The ID of the actor that can bypass a ruleset. If `actor_type` is `OrganizationAdmin`, this should be `1`. If `actor_type` is `DeployKey`, this should be null. `OrganizationAdmin` is not applicable for personal repositories. + * */ actor_id?: number | null; /** * @description The type of actor that can bypass a ruleset. @@ -50990,6 +53983,7 @@ export interface components { /** * Organization ruleset conditions * @description Conditions for an organization ruleset. The conditions object should contain both `repository_name` and `ref_name` properties or both `repository_id` and `ref_name` properties. + * */ "org-ruleset-conditions": | (components["schemas"]["repository-ruleset-conditions"] & @@ -51800,10 +54794,8 @@ export interface components { resolution_comment?: string | null; /** @description The type of secret that secret scanning detected. */ secret_type?: string; - /** - * @description User-friendly name for the detected secret, matching the `secret_type`. - * For a list of built-in patterns, see "[Supported secret scanning patterns](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." - */ + /** @description User-friendly name for the detected secret, matching the `secret_type`. + * For a list of built-in patterns, see "[Supported secret scanning patterns](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." */ secret_type_display_name?: string; /** * @description The token status as of the latest validity check. @@ -52280,34 +55272,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -52523,34 +55515,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -53298,7 +56290,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53550,7 +56542,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53802,7 +56794,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -54085,7 +57077,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -54337,7 +57329,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -56139,22 +59131,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were disabled for a repository. - */ "branch-protection-configuration/disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56171,6 +59152,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56180,20 +59163,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were enabled for a repository. - */ "branch-protection-configuration/enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56210,6 +59189,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56219,18 +59200,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56251,6 +59230,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56260,18 +59241,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56292,6 +59271,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56301,18 +59282,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/enterprise-server@3.14/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56333,6 +59312,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56342,22 +59323,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning push protection bypass request was cancelled. - */ "exemption-request-secret-scanning/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56374,6 +59349,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56383,22 +59360,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning bypass request was completed. - */ "exemption-request-secret-scanning/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56415,6 +59386,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56424,22 +59397,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning push protection bypass request was created. - */ "exemption-request-secret-scanning/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56456,6 +59423,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56465,22 +59434,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A secret scanning push protection bypass response was dismissed. - */ "exemption-request-secret-scanning/response-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56497,6 +59460,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56506,22 +59471,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity related to a user's request to bypass secret scanning push protection. - * - * For more information, see "[Enabling delegated bypass for push protection](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#enabling-delegated-bypass-for-push-protection)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * - * Note: Delegated bypass for push protection is currently in beta and subject to change. - * @description A response either approving or rejecting the secret scanning push protection bypass request was submitted. - */ "exemption-request-secret-scanning/response-submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56538,6 +59497,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56547,13 +59508,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](https://docs.github.com/enterprise-server@3.14/admin/enterprise-management/caching-repositories/about-repository-caching)." */ "cache-sync": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56574,6 +59538,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56583,25 +59549,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56622,6 +59579,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56631,25 +59590,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56670,6 +59620,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56679,25 +59631,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/enterprise-server@3.14/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56718,6 +59661,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56727,25 +59672,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/enterprise-server@3.14/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56766,6 +59702,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56775,25 +59713,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.14/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56814,6 +59743,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56823,25 +59754,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.14/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/enterprise-server@3.14/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/enterprise-server@3.14/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56862,6 +59784,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56871,25 +59795,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/enterprise-server@3.14/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/enterprise-server@3.14/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/enterprise-server@3.14/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/enterprise-server@3.14/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56910,6 +59825,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56919,18 +59836,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56951,6 +59866,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -56960,18 +59877,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -56992,6 +59907,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57001,18 +59918,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57033,6 +59948,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57042,18 +59959,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57074,6 +59989,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57083,18 +60000,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57115,6 +60030,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57124,18 +60041,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/enterprise-server@3.14/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/enterprise-server@3.14/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57156,6 +60071,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57165,20 +60082,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/enterprise-server@3.14/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57199,6 +60112,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57208,21 +60123,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57243,6 +60153,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57252,21 +60164,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57287,6 +60194,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57296,23 +60205,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. - */ "dependabot-alert/auto-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57333,6 +60235,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57342,23 +60246,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. - */ "dependabot-alert/auto-reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57379,6 +60276,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57388,23 +60287,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57425,6 +60317,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57434,23 +60328,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57471,6 +60358,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57480,23 +60369,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57517,6 +60399,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57526,23 +60410,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57563,6 +60440,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57572,23 +60451,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/enterprise-server@3.14/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57609,6 +60481,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57618,18 +60492,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.14/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.14/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57650,6 +60522,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57659,18 +60533,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/enterprise-server@3.14/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/enterprise-server@3.14/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57691,6 +60563,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57700,20 +60574,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57734,6 +60604,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57743,18 +60615,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/enterprise-server@3.14/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57775,6 +60645,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57784,20 +60656,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57818,6 +60686,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57827,20 +60697,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57861,6 +60727,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57870,20 +60738,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57904,6 +60768,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57913,23 +60779,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/enterprise-server@3.14/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/enterprise-server@3.14/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57950,6 +60809,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -57959,23 +60820,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -57996,6 +60850,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58005,23 +60861,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58042,6 +60891,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58051,23 +60902,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58088,6 +60932,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58097,23 +60943,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58134,6 +60973,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58143,23 +60984,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58180,6 +61014,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58189,23 +61025,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58226,6 +61055,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58235,23 +61066,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58272,6 +61096,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58281,23 +61107,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58318,6 +61137,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58327,23 +61148,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58364,6 +61178,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58373,23 +61189,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58410,6 +61219,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58419,23 +61230,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58456,6 +61260,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58465,23 +61271,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58502,6 +61301,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58511,23 +61312,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58548,6 +61342,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58557,23 +61353,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58594,6 +61383,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58603,23 +61394,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58640,6 +61424,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58649,23 +61435,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58686,6 +61465,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58695,23 +61476,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58732,6 +61506,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58741,23 +61517,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/enterprise-server@3.14/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58778,6 +61547,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58787,16 +61558,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.14/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was disabled. - */ "enterprise/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58817,6 +61588,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58826,16 +61599,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to anonymous Git read access in an enterprise. For more information, see "[Enforcing repository management policies in your enterprise](https://docs.github.com/enterprise-server@3.14/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)." - * @description Anonymous Git read access was enabled. - */ "enterprise/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58856,6 +61629,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58865,17 +61640,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/enterprise-server@3.14/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/enterprise-server@3.14/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58896,6 +61670,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58905,20 +61681,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/enterprise-server@3.14/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58939,6 +61711,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58948,17 +61722,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/enterprise-server@3.14/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -58979,6 +61752,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -58988,18 +61763,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59020,6 +61793,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59029,18 +61804,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59061,6 +61834,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59070,18 +61845,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59102,6 +61875,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59111,18 +61886,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59143,6 +61916,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59152,18 +61927,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59184,6 +61957,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59193,18 +61968,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59225,6 +61998,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59234,16 +62009,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59264,6 +62039,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59273,18 +62050,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/enterprise-server@3.14/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#app) or "[Apps](https://docs.github.com/enterprise-server@3.14/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59305,6 +62080,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59314,20 +62091,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.14/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59348,6 +62121,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59357,20 +62132,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.14/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59391,6 +62162,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59400,20 +62173,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/enterprise-server@3.14/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/enterprise-server@3.14/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59434,6 +62203,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59443,20 +62214,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59477,6 +62244,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59486,20 +62255,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59520,6 +62285,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59529,20 +62296,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59563,6 +62326,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59572,20 +62337,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59606,6 +62367,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59615,20 +62378,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59649,6 +62408,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59658,20 +62419,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59692,6 +62449,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59701,20 +62460,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59735,6 +62490,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59744,20 +62501,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59778,6 +62531,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59787,20 +62542,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59821,6 +62572,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59830,20 +62583,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59864,6 +62613,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59873,20 +62624,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59907,6 +62654,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59916,20 +62665,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59950,6 +62695,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59959,20 +62706,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59993,6 +62736,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60002,20 +62747,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60036,6 +62777,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60045,20 +62788,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60079,6 +62818,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60088,20 +62829,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/enterprise-server@3.14/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/enterprise-server@3.14/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60122,6 +62859,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60131,20 +62870,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.14/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60165,6 +62900,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60174,20 +62911,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.14/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60208,6 +62941,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60217,20 +62952,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#label) or "[Labels](https://docs.github.com/enterprise-server@3.14/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60251,6 +62982,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60260,18 +62993,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.14/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.14/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60292,6 +63023,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60301,18 +63034,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.14/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.14/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60333,6 +63064,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60342,18 +63075,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/enterprise-server@3.14/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/enterprise-server@3.14/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60374,6 +63105,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60383,18 +63116,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.14/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60415,6 +63146,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60424,18 +63157,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#team) or "[Team members](https://docs.github.com/enterprise-server@3.14/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60456,6 +63187,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60465,18 +63198,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60497,6 +63228,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60506,20 +63239,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60540,6 +63269,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60549,20 +63280,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60583,6 +63310,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60592,20 +63321,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60626,6 +63351,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60635,20 +63362,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60669,6 +63392,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60678,20 +63403,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/enterprise-server@3.14/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/enterprise-server@3.14/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60712,6 +63433,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60721,20 +63444,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60755,6 +63474,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60764,20 +63485,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60798,6 +63515,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60807,20 +63526,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60841,6 +63556,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60850,20 +63567,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60884,6 +63597,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60893,20 +63608,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/enterprise-server@3.14/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/enterprise-server@3.14/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60927,6 +63638,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60936,18 +63649,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60968,6 +63679,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60977,18 +63690,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61009,6 +63720,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61018,17 +63731,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/enterprise-server@3.14/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/enterprise-server@3.14/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61049,6 +63761,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61058,21 +63772,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61089,6 +63798,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61098,21 +63809,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61129,6 +63835,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61138,21 +63846,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61169,6 +63872,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61178,21 +63883,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/enterprise-server@3.14/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61209,6 +63909,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61218,13 +63920,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61245,6 +63950,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61254,22 +63961,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61290,6 +63991,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61299,22 +64002,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61335,6 +64032,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61344,22 +64043,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61380,6 +64073,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61389,22 +64084,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61425,6 +64114,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61434,22 +64125,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61470,6 +64155,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61479,22 +64166,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61515,6 +64196,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61524,22 +64207,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61560,6 +64237,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61569,22 +64248,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61605,6 +64278,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61614,22 +64289,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61650,6 +64319,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61659,22 +64330,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61695,6 +64360,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61704,22 +64371,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61740,6 +64401,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61749,22 +64412,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61785,6 +64442,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61794,22 +64453,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61830,6 +64483,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61839,22 +64494,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/enterprise-server@3.14/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/enterprise-server@3.14/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61875,6 +64524,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61884,23 +64535,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61921,6 +64565,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61930,23 +64576,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61967,6 +64606,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61976,23 +64617,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62013,6 +64647,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62022,23 +64658,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62059,6 +64688,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62068,23 +64699,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62105,6 +64729,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62114,23 +64740,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62151,6 +64770,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62160,23 +64781,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62197,6 +64811,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62206,23 +64822,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62243,6 +64852,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62252,23 +64863,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62289,6 +64893,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62298,23 +64904,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62335,6 +64934,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62344,23 +64945,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62381,6 +64975,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62390,23 +64986,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/enterprise-server@3.14/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62427,6 +65016,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62436,17 +65027,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/enterprise-server@3.14/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62467,6 +65057,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62476,20 +65068,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62510,6 +65098,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62519,20 +65109,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62553,6 +65139,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62562,20 +65150,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62596,6 +65180,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62605,20 +65191,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62639,6 +65221,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62648,20 +65232,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62682,6 +65262,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62691,20 +65273,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62725,6 +65303,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62734,20 +65314,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62768,6 +65344,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62777,20 +65355,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62811,6 +65385,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62820,20 +65396,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62854,6 +65426,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62863,20 +65437,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62897,6 +65467,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62906,20 +65478,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62940,6 +65508,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62949,20 +65519,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62983,6 +65549,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62992,20 +65560,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63026,6 +65590,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63035,20 +65601,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63069,6 +65631,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63078,20 +65642,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63112,6 +65672,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63121,20 +65683,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63155,6 +65713,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63164,20 +65724,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.14/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63198,6 +65754,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63207,20 +65765,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.14/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63241,6 +65795,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63250,20 +65806,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63284,6 +65836,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63293,20 +65847,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63327,6 +65877,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63336,20 +65888,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/enterprise-server@3.14/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63370,6 +65918,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63379,20 +65929,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63413,6 +65959,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63422,20 +65970,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/enterprise-server@3.14/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63456,6 +66000,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63465,20 +66011,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63499,6 +66041,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63508,20 +66052,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63542,6 +66082,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63551,20 +66093,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63585,6 +66123,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63594,20 +66134,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/enterprise-server@3.14/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/enterprise-server@3.14/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63628,6 +66164,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63637,22 +66175,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63673,6 +66205,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63682,21 +66216,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63717,6 +66246,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63726,21 +66257,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/enterprise-server@3.14/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#package) or "[Packages](https://docs.github.com/enterprise-server@3.14/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63761,6 +66287,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63770,18 +66298,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63802,6 +66328,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63811,18 +66339,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63843,6 +66369,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63852,18 +66380,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63884,6 +66410,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63893,18 +66421,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63925,6 +66451,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63934,18 +66462,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63966,6 +66492,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63975,18 +66503,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64007,6 +66533,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64016,18 +66544,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/enterprise-server@3.14/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#release) or "[Releases](https://docs.github.com/enterprise-server@3.14/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64048,6 +66574,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64057,18 +66585,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64089,6 +66615,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64098,18 +66626,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64130,6 +66656,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64139,18 +66667,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64171,6 +66697,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64180,18 +66708,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64212,6 +66738,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64221,18 +66749,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64253,6 +66779,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64262,17 +66790,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/enterprise-server@3.14/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64293,6 +66820,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64302,18 +66831,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64334,6 +66861,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64343,18 +66872,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64375,6 +66902,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64384,18 +66913,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64416,6 +66943,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64425,18 +66954,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64457,6 +66984,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64466,20 +66995,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was created. - */ "repository-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64496,6 +67021,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64505,20 +67032,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was deleted. - */ "repository-ruleset/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64535,6 +67058,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64544,20 +67069,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/enterprise-server@3.14/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/enterprise-server@3.14/rest/repos/rules)" and "[Organization rules](https://docs.github.com/enterprise-server@3.14/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was edited. - */ "repository-ruleset/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64574,6 +67095,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64583,18 +67106,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64615,6 +67136,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64624,18 +67147,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/enterprise-server@3.14/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/enterprise-server@3.14/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64656,6 +67177,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64665,19 +67188,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64698,6 +67218,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64707,19 +67229,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64740,6 +67259,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64749,19 +67270,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64782,6 +67300,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64791,19 +67311,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64824,6 +67341,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64833,20 +67352,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64867,6 +67382,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64876,22 +67393,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64912,6 +67423,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64921,20 +67434,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64955,6 +67464,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64964,20 +67475,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64998,6 +67505,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65007,20 +67516,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/enterprise-server@3.14/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/enterprise-server@3.14/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was validated. - */ "secret-scanning-alert/validated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65041,6 +67546,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65050,18 +67557,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.14/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65082,6 +67587,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65091,18 +67598,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.14/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65123,6 +67628,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65132,18 +67639,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/enterprise-server@3.14/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/enterprise-server@3.14/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/enterprise-server@3.14/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65164,6 +67669,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65173,17 +67680,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/enterprise-server@3.14/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65204,6 +67710,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65213,20 +67721,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65247,6 +67751,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65256,18 +67762,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65288,6 +67792,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65297,18 +67803,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65329,6 +67833,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65338,20 +67844,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65372,6 +67874,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65381,18 +67885,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65413,6 +67915,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65422,18 +67926,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/enterprise-server@3.14/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/enterprise-server@3.14/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65454,6 +67956,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65463,18 +67967,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.14/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.14/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65495,6 +67997,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65504,18 +68008,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/enterprise-server@3.14/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/enterprise-server@3.14/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65536,6 +68038,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65545,17 +68049,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/enterprise-server@3.14/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/enterprise-server@3.14/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65576,6 +68079,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65585,20 +68090,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/enterprise-server@3.14/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65619,6 +68120,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65628,19 +68131,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65661,6 +68161,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65670,19 +68172,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65703,6 +68202,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65712,19 +68213,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65745,6 +68243,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65754,19 +68254,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65787,6 +68284,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65796,19 +68295,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/enterprise-server@3.14/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65829,6 +68325,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65838,16 +68336,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was added to the enterprise. - */ "user/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65868,6 +68366,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65877,16 +68377,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was removed from the enterprise. - */ "user/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65907,6 +68407,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65916,18 +68418,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/enterprise-server@3.14/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/enterprise-server@3.14/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65948,6 +68448,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65957,19 +68459,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/enterprise-server@3.14/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65990,6 +68489,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65999,20 +68500,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66033,6 +68530,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66042,20 +68541,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66076,6 +68571,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66085,20 +68582,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66119,6 +68612,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66128,20 +68623,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/enterprise-server@3.14/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66162,6 +68653,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66171,20 +68664,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.14/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66205,6 +68694,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66214,20 +68705,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.14/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66248,6 +68735,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66257,20 +68746,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/enterprise-server@3.14/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/enterprise-server@3.14/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/enterprise-server@3.14/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66291,6 +68776,8 @@ export interface operations { /** @example ghes.github.com */ "X-GitHub-Enterprise-Host": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66300,7 +68787,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types-github.ae/package.json b/packages/openapi-webhooks-types-github.ae/package.json index 77fa1e9..f62761c 100644 --- a/packages/openapi-webhooks-types-github.ae/package.json +++ b/packages/openapi-webhooks-types-github.ae/package.json @@ -3,7 +3,7 @@ "description": "Generated TypeScript definitions based on GitHub's OpenAPI spec for github.ae", "repository": { "type": "git", - "url": "https://github.com/octokit/openapi-webhooks.git", + "url": "git+https://github.com/octokit/openapi-webhooks.git", "directory": "packages/openapi-webhooks-types-github.ae" }, "publishConfig": { diff --git a/packages/openapi-webhooks-types-github.ae/types.d.ts b/packages/openapi-webhooks-types-github.ae/types.d.ts index ea0dd43..6b78e59 100644 --- a/packages/openapi-webhooks-types-github.ae/types.d.ts +++ b/packages/openapi-webhooks-types-github.ae/types.d.ts @@ -3,2222 +3,4826 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/github-ae@latest/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/github-ae@latest/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/github-ae@latest/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/github-ae@latest/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/github-ae@latest/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/github-ae@latest/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/github-ae@latest/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/github-ae@latest/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/github-ae@latest/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/github-ae@latest/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/github-ae@latest/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/github-ae@latest/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/github-ae@latest/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/github-ae@latest/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/github-ae@latest/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Note**: This event will not occur when more than three tags are deleted at once. - */ + * **Note**: This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. */ post: operations["dependabot-alert/auto-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. */ post: operations["dependabot-alert/auto-reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. + * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/github-ae@latest/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/github-ae@latest/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/github-ae@latest/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/github-ae@latest/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/github-ae@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/github-ae@latest/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. + * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/github-ae@latest/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/github-ae@latest/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/github-ae@latest/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/github-ae@latest/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/github-ae@latest/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/github-ae@latest/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/github-ae@latest/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/github-ae@latest/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/github-ae@latest/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/github-ae@latest/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/github-ae@latest/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#label) or "[Labels](https://docs.github.com/github-ae@latest/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#label) or "[Labels](https://docs.github.com/github-ae@latest/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#label) or "[Labels](https://docs.github.com/github-ae@latest/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/github-ae@latest/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/github-ae@latest/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/github-ae@latest/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/github-ae@latest/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/github-ae@latest/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/github-ae@latest/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#team) or "[Team members](https://docs.github.com/github-ae@latest/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#team) or "[Team members](https://docs.github.com/github-ae@latest/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/github-ae@latest/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/github-ae@latest/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/github-ae@latest/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/github-ae@latest/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/github-ae@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/github-ae@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/github-ae@latest/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/github-ae@latest/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/github-ae@latest/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Note**: An event will not be created when more than three tags are pushed at once. - */ + * **Note**: An event will not be created when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * **Note**: GitHub recommends that you use the newer `package` event instead. + * **Note**: GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * **Note**: GitHub recommends that you use the newer `package` event instead. + * **Note**: GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-anonymous-access-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." */ post: operations["repository/anonymous-access-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/github-ae@latest/rest/repos/repos#create-a-repository-dispatch-event). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was marked as revoked. */ post: operations["secret-scanning-alert/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/github-ae@latest/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/github-ae@latest/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/github-ae@latest/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/github-ae@latest/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/github-ae@latest/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/github-ae@latest/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/github-ae@latest/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/github-ae@latest/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/github-ae@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/github-ae@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was added to the enterprise. */ post: operations["user/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "user-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to user accounts in an enterprise. * @description A user account was removed from the enterprise. */ post: operations["user/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/github-ae@latest/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/github-ae@latest/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/github-ae@latest/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/github-ae@latest/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/github-ae@latest/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/github-ae@latest/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/github-ae@latest/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/github-ae@latest/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/github-ae@latest/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/github-ae@latest/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/github-ae@latest/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/github-ae@latest/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/github-ae@latest/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/github-ae@latest/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/github-ae@latest/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/github-ae@latest/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection rule created event */ @@ -2296,8 +4900,9 @@ export interface components { /** * Enterprise * @description An enterprise on GitHub. Webhook payloads contain the `enterprise` property when the webhook is configured - * on an enterprise account or an organization that's part of an enterprise account. For more information, - * see "[About enterprise accounts](https://docs.github.com/github-ae@latest/admin/overview/about-enterprise-accounts)." + * on an enterprise account or an organization that's part of an enterprise account. For more information, + * see "[About enterprise accounts](https://docs.github.com/github-ae@latest/admin/overview/about-enterprise-accounts)." + * */ "enterprise-webhooks": { /** @description A short description of the enterprise. */ @@ -2326,8 +4931,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/github-ae@latest/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/github-ae@latest/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2338,7 +4943,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2360,7 +4965,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @description Unique identifier of the repository */ @@ -3000,9 +5605,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3010,7 +5615,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5064,10 +7670,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5101,16 +7707,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5120,7 +7726,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5134,14 +7740,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5151,7 +7757,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5175,8 +7781,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5194,37 +7800,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert auto-reopened event */ "webhook-dependabot-alert-auto-reopened": { /** @enum {string} */ @@ -5943,14 +8549,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -7784,7 +10387,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -8738,8 +11342,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9737,7 +12341,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -9977,11 +12581,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -10044,11 +12652,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -17729,7 +20337,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19939,7 +22547,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24045,19 +26653,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -25872,17 +28477,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25949,7 +28554,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25957,9 +28562,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25969,8 +28574,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26215,17 +28820,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26292,7 +28897,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26300,9 +28905,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -26312,8 +28917,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26535,9 +29140,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26572,8 +29176,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -26623,9 +29227,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27084,17 +29687,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27161,7 +29764,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27169,9 +29772,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27181,8 +29784,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27427,17 +30030,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27504,7 +30107,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27512,9 +30115,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27524,8 +30127,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27747,9 +30350,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27784,8 +30386,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -27835,9 +30437,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -28297,17 +30898,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28374,7 +30975,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28382,9 +30983,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28394,8 +30995,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28640,17 +31241,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28717,7 +31318,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28725,9 +31326,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28737,8 +31338,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28960,9 +31561,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -28997,8 +31597,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -29048,9 +31648,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29186,31 +31785,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29247,31 +31846,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29633,17 +32232,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29710,7 +32309,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29718,9 +32317,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29730,8 +32329,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29976,17 +32575,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30053,7 +32652,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30061,9 +32660,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30073,8 +32672,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30296,9 +32895,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -30333,8 +32931,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -30384,9 +32982,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -30540,31 +33137,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30942,17 +33539,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31019,7 +33616,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31027,9 +33624,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31039,8 +33636,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31285,17 +33882,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31362,7 +33959,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31370,9 +33967,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31382,8 +33979,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31605,9 +34202,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31642,8 +34238,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -31693,9 +34289,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32155,17 +34750,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32232,7 +34827,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32240,9 +34835,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32252,8 +34847,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32498,17 +35093,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -32575,7 +35170,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -32583,9 +35178,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -32595,8 +35190,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32818,9 +35413,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -32855,8 +35449,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -32906,9 +35500,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -33368,17 +35961,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33445,7 +36038,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33453,9 +36046,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33465,8 +36058,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33711,17 +36304,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33788,7 +36381,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33796,9 +36389,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33808,8 +36401,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34031,9 +36624,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34068,8 +36660,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -34119,9 +36711,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34256,31 +36847,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34317,31 +36908,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34378,31 +36969,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34913,17 +37504,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -34990,7 +37581,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -34998,9 +37589,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -35010,8 +37601,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -35249,17 +37840,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35326,7 +37917,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35334,9 +37925,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -35346,8 +37937,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -35524,9 +38115,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -35561,8 +38151,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -35612,9 +38202,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -36217,17 +38806,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36294,7 +38883,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36302,9 +38891,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36314,8 +38903,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36553,17 +39142,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36630,7 +39219,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36638,9 +39227,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36650,8 +39239,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36828,9 +39417,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36865,8 +39453,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -36916,9 +39504,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -37528,17 +40115,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37605,7 +40192,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37613,9 +40200,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37625,8 +40212,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37864,17 +40451,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -37941,7 +40528,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -37949,9 +40536,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37961,8 +40548,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -38139,9 +40726,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -38176,8 +40762,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -38227,9 +40813,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38680,17 +41265,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -38757,7 +41342,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38765,9 +41350,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -38777,8 +41362,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39016,17 +41601,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39093,7 +41678,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39101,9 +41686,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39113,8 +41698,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39291,9 +41876,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39328,8 +41912,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39379,9 +41963,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39974,7 +42557,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40261,7 +42844,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40432,9 +43015,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40469,8 +43051,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -40520,9 +43102,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -40708,9 +43289,8 @@ export interface components { sender: components["schemas"]["simple-user-webhooks"]; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -41058,17 +43638,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41135,7 +43715,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41394,17 +43974,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41471,7 +44051,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41479,9 +44059,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41491,8 +44071,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41714,9 +44294,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -41751,8 +44330,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -41802,9 +44381,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -41951,8 +44529,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -42300,17 +44878,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -42377,7 +44955,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42385,9 +44963,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -42397,8 +44975,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -42643,17 +45221,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -42720,7 +45298,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42728,9 +45306,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -42740,8 +45318,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -42963,9 +45541,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43000,8 +45577,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -43051,9 +45628,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43218,13 +45794,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -43572,17 +46145,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -43649,7 +46222,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43657,9 +46230,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -43669,8 +46242,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -43915,17 +46488,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -43992,7 +46565,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44000,9 +46573,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44012,8 +46585,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -44235,9 +46808,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -44272,8 +46844,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -44323,9 +46895,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -44472,8 +47043,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; enterprise?: components["schemas"]["enterprise-webhooks"]; @@ -44821,17 +47392,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44898,7 +47469,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44906,9 +47477,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44918,8 +47489,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45164,17 +47735,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -45241,7 +47812,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45249,9 +47820,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -45261,8 +47832,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -45484,9 +48055,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45521,8 +48091,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -45572,9 +48142,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45739,9 +48308,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -46088,17 +48655,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46165,7 +48732,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46173,9 +48740,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46185,8 +48752,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46424,17 +48991,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -46501,7 +49068,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46509,9 +49076,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -46521,8 +49088,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -46699,9 +49266,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46736,8 +49302,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -46787,9 +49353,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -47380,7 +49945,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47674,7 +50239,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47847,9 +50412,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -47884,8 +50448,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -47935,9 +50499,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48600,7 +51163,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48894,7 +51457,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49067,9 +51630,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -49104,8 +51666,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -49155,9 +51717,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -49765,17 +52326,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -49842,7 +52403,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49850,9 +52411,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -49862,8 +52423,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -50178,7 +52739,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -50186,9 +52747,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -50198,8 +52759,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -50421,9 +52982,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -50458,8 +53018,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -50509,9 +53069,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -51008,17 +53567,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -51085,7 +53644,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -51093,9 +53652,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -51105,8 +53664,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -51351,17 +53910,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -51428,7 +53987,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -51436,9 +53995,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -51448,8 +54007,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -51671,9 +54230,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -51708,8 +54266,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -51759,9 +54317,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -52237,17 +54794,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -52314,7 +54871,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52322,9 +54879,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -52334,8 +54891,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -52650,7 +55207,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52658,9 +55215,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -52670,8 +55227,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -52893,9 +55450,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -52930,8 +55486,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -52981,9 +55537,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -53443,17 +55998,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -53520,7 +56075,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53528,9 +56083,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -53540,8 +56095,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -53786,17 +56341,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -53863,7 +56418,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -53871,9 +56426,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -53883,8 +56438,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -54106,9 +56661,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -54143,8 +56697,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -54194,9 +56748,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -54648,7 +57201,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -54770,19 +57323,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -54795,7 +57352,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -54807,21 +57365,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -58440,7 +60996,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -58753,7 +61309,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -59066,7 +61622,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -59410,7 +61966,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -59723,7 +62279,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -62119,20 +64675,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/github-ae@latest/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/github-ae@latest/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62149,6 +64696,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62158,18 +64707,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/github-ae@latest/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/github-ae@latest/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62186,6 +64733,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62195,18 +64744,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/github-ae@latest/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/github-ae@latest/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62223,6 +64770,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62232,24 +64781,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62266,6 +64807,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62275,24 +64818,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62309,6 +64844,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62318,24 +64855,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/github-ae@latest/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62352,6 +64881,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62361,24 +64892,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/github-ae@latest/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62395,6 +64918,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62404,24 +64929,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/github-ae@latest/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62438,6 +64955,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62447,24 +64966,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/github-ae@latest/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/github-ae@latest/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/github-ae@latest/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62481,6 +64992,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62490,24 +65003,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/github-ae@latest/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/github-ae@latest/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * **Note**: The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/github-ae@latest/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/github-ae@latest/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62524,6 +65029,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62533,18 +65040,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62561,6 +65066,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62570,18 +65077,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62598,6 +65103,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62607,18 +65114,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62635,6 +65140,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62644,18 +65151,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62672,6 +65177,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62681,18 +65188,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62709,6 +65214,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62718,18 +65225,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/github-ae@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/github-ae@latest/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62746,6 +65251,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62755,20 +65262,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/github-ae@latest/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62785,6 +65288,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62794,21 +65299,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62825,6 +65325,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62834,20 +65336,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Note**: This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62864,6 +65362,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62873,22 +65373,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. - */ "dependabot-alert/auto-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62905,6 +65399,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62914,22 +65410,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. - */ "dependabot-alert/auto-reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62946,6 +65436,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62955,22 +65447,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62987,6 +65473,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62996,22 +65484,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63028,6 +65510,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63037,22 +65521,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63069,6 +65547,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63078,22 +65558,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63110,6 +65584,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63119,22 +65595,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/github-ae@latest/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/github-ae@latest/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * **Note**: Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63151,6 +65621,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63160,18 +65632,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/github-ae@latest/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/github-ae@latest/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63188,6 +65658,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63197,18 +65669,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/github-ae@latest/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/github-ae@latest/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63225,6 +65695,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63234,20 +65706,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63264,6 +65732,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63273,18 +65743,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/github-ae@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/github-ae@latest/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63301,6 +65769,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63310,20 +65780,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63340,6 +65806,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63349,20 +65817,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63379,6 +65843,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63388,20 +65854,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63418,6 +65880,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63427,20 +65891,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/github-ae@latest/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/github-ae@latest/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63457,6 +65917,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63466,22 +65928,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63498,6 +65954,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63507,22 +65965,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63539,6 +65991,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63548,22 +66002,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63580,6 +66028,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63589,22 +66039,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63621,6 +66065,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63630,22 +66076,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63662,6 +66102,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63671,22 +66113,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63703,6 +66139,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63712,22 +66150,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63744,6 +66176,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63753,22 +66187,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63785,6 +66213,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63794,22 +66224,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63826,6 +66250,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63835,22 +66261,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63867,6 +66287,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63876,22 +66298,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63908,6 +66324,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63917,22 +66335,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63949,6 +66361,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63958,22 +66372,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63990,6 +66398,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63999,22 +66409,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64031,6 +66435,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64040,22 +66446,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64072,6 +66472,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64081,22 +66483,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/github-ae@latest/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * **Note**: Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64113,6 +66509,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64122,17 +66520,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/github-ae@latest/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/github-ae@latest/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64149,6 +66546,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64158,20 +66557,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/github-ae@latest/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64188,6 +66583,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64197,17 +66594,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/github-ae@latest/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64224,6 +66620,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64233,18 +66631,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64261,6 +66657,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64270,18 +66668,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64298,6 +66694,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64307,18 +66705,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64335,6 +66731,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64344,18 +66742,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64372,6 +66768,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64381,18 +66779,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64409,6 +66805,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64418,18 +66816,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64446,6 +66842,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64455,16 +66853,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64481,6 +66879,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64490,18 +66890,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/github-ae@latest/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#app) or "[Apps](https://docs.github.com/github-ae@latest/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64518,6 +66916,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64527,20 +66927,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/github-ae@latest/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64557,6 +66953,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64566,20 +66964,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/github-ae@latest/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64596,6 +66990,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64605,20 +67001,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/github-ae@latest/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/github-ae@latest/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64635,6 +67027,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64644,20 +67038,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64674,6 +67064,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64683,20 +67075,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64713,6 +67101,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64722,20 +67112,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64752,6 +67138,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64761,20 +67149,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64791,6 +67175,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64800,20 +67186,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64830,6 +67212,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64839,20 +67223,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64869,6 +67249,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64878,20 +67260,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64908,6 +67286,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64917,20 +67297,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64947,6 +67323,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64956,20 +67334,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64986,6 +67360,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64995,20 +67371,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65025,6 +67397,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65034,20 +67408,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65064,6 +67434,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65073,20 +67445,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65103,6 +67471,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65112,20 +67482,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65142,6 +67508,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65151,20 +67519,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65181,6 +67545,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65190,20 +67556,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65220,6 +67582,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65229,20 +67593,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/github-ae@latest/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/github-ae@latest/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65259,6 +67619,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65268,20 +67630,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#label) or "[Labels](https://docs.github.com/github-ae@latest/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65298,6 +67656,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65307,20 +67667,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#label) or "[Labels](https://docs.github.com/github-ae@latest/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65337,6 +67693,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65346,20 +67704,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#label) or "[Labels](https://docs.github.com/github-ae@latest/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65376,6 +67730,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65385,18 +67741,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/github-ae@latest/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/github-ae@latest/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65413,6 +67767,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65422,18 +67778,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/github-ae@latest/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/github-ae@latest/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65450,6 +67804,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65459,18 +67815,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/github-ae@latest/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/github-ae@latest/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65487,6 +67841,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65496,18 +67852,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#team) or "[Team members](https://docs.github.com/github-ae@latest/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65524,6 +67878,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65533,18 +67889,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#team) or "[Team members](https://docs.github.com/github-ae@latest/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65561,6 +67915,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65570,18 +67926,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65598,6 +67952,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65607,20 +67963,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65637,6 +67989,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65646,20 +68000,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65676,6 +68026,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65685,20 +68037,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65715,6 +68063,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65724,20 +68074,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65754,6 +68100,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65763,20 +68111,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/github-ae@latest/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/github-ae@latest/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65793,6 +68137,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65802,20 +68148,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65832,6 +68174,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65841,20 +68185,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65871,6 +68211,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65880,20 +68222,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65910,6 +68248,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65919,20 +68259,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65949,6 +68285,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65958,20 +68296,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/github-ae@latest/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/github-ae@latest/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65988,6 +68322,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65997,18 +68333,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66025,6 +68359,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66034,18 +68370,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66062,6 +68396,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66071,17 +68407,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/github-ae@latest/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/github-ae@latest/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66098,6 +68433,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66107,13 +68444,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66130,6 +68470,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66139,22 +68481,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66171,6 +68507,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66180,22 +68518,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66212,6 +68544,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66221,22 +68555,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66253,6 +68581,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66262,22 +68592,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66294,6 +68618,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66303,22 +68629,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66335,6 +68655,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66344,22 +68666,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66376,6 +68692,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66385,22 +68703,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66417,6 +68729,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66426,22 +68740,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66458,6 +68766,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66467,22 +68777,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66499,6 +68803,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66508,22 +68814,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66540,6 +68840,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66549,22 +68851,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66581,6 +68877,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66590,22 +68888,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66622,6 +68914,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66631,22 +68925,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66663,6 +68951,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66672,22 +68962,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/github-ae@latest/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/github-ae@latest/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66704,6 +68988,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66713,22 +68999,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66745,6 +69025,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66754,22 +69036,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66786,6 +69062,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66795,22 +69073,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66827,6 +69099,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66836,22 +69110,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66868,6 +69136,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66877,22 +69147,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/github-ae@latest/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * **Note**: Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66909,6 +69173,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66918,17 +69184,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/github-ae@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66945,6 +69210,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66954,20 +69221,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66984,6 +69247,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66993,20 +69258,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67023,6 +69284,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67032,20 +69295,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67062,6 +69321,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67071,20 +69332,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67101,6 +69358,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67110,20 +69369,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67140,6 +69395,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67149,20 +69406,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67179,6 +69432,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67188,20 +69443,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67218,6 +69469,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67227,20 +69480,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67257,6 +69506,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67266,20 +69517,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67296,6 +69543,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67305,20 +69554,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67335,6 +69580,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67344,20 +69591,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67374,6 +69617,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67383,20 +69628,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67413,6 +69654,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67422,20 +69665,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67452,6 +69691,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67461,20 +69702,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67491,6 +69728,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67500,20 +69739,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67530,6 +69765,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67539,20 +69776,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67569,6 +69802,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67578,20 +69813,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/github-ae@latest/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67608,6 +69839,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67617,20 +69850,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/github-ae@latest/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67647,6 +69876,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67656,20 +69887,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67686,6 +69913,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67695,20 +69924,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67725,6 +69950,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67734,20 +69961,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/github-ae@latest/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67764,6 +69987,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67773,20 +69998,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67803,6 +70024,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67812,20 +70035,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/github-ae@latest/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67842,6 +70061,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67851,20 +70072,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67881,6 +70098,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67890,20 +70109,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67920,6 +70135,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67929,20 +70146,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67959,6 +70172,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67968,20 +70183,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/github-ae@latest/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/github-ae@latest/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67998,6 +70209,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68007,21 +70220,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Note**: An event will not be created when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68038,6 +70246,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68047,20 +70257,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * **Note**: GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68077,6 +70283,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68086,20 +70294,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/github-ae@latest/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#package) or "[Packages](https://docs.github.com/github-ae@latest/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * **Note**: GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68116,6 +70320,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68125,18 +70331,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68153,6 +70357,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68162,18 +70368,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68190,6 +70394,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68199,18 +70405,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68227,6 +70431,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68236,18 +70442,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68264,6 +70468,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68273,18 +70479,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68301,6 +70505,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68310,18 +70516,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68338,6 +70542,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68347,18 +70553,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/github-ae@latest/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#release) or "[Releases](https://docs.github.com/github-ae@latest/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68375,6 +70579,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68384,18 +70590,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone disabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68412,6 +70616,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68421,18 +70627,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone enabled anonymous Git read access to the repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)." - */ "repository/anonymous-access-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68449,6 +70653,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68458,18 +70664,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68486,6 +70690,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68495,18 +70701,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68523,6 +70727,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68532,18 +70738,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68560,6 +70764,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68569,18 +70775,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/github-ae@latest/rest/repos/repos#create-a-repository-dispatch-event). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68597,6 +70801,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68606,18 +70812,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68634,6 +70838,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68643,18 +70849,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68671,6 +70875,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68680,18 +70886,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68708,6 +70912,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68717,18 +70923,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68745,6 +70949,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68754,18 +70960,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68782,6 +70986,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68791,18 +70997,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/github-ae@latest/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/github-ae@latest/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68819,6 +71023,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68828,20 +71034,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68858,6 +71060,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68867,22 +71071,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68899,6 +71097,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68908,20 +71108,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68938,6 +71134,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68947,20 +71145,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68977,6 +71171,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68986,20 +71182,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/github-ae@latest/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/github-ae@latest/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was marked as revoked. - */ "secret-scanning-alert/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69016,6 +71208,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69025,17 +71219,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/github-ae@latest/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69052,6 +71245,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69061,20 +71256,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69091,6 +71282,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69100,18 +71293,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69128,6 +71319,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69137,18 +71330,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69165,6 +71356,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69174,20 +71367,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69204,6 +71393,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69213,18 +71404,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69241,6 +71430,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69250,18 +71441,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/github-ae@latest/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/github-ae@latest/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69278,6 +71467,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69287,18 +71478,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/github-ae@latest/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/github-ae@latest/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69315,6 +71504,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69324,18 +71515,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/github-ae@latest/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/github-ae@latest/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69352,6 +71541,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69361,17 +71552,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/github-ae@latest/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/github-ae@latest/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69388,6 +71578,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69397,20 +71589,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/github-ae@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69427,6 +71615,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69436,19 +71626,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69465,6 +71652,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69474,19 +71663,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69503,6 +71689,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69512,19 +71700,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69541,6 +71726,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69550,19 +71737,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69579,6 +71763,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69588,19 +71774,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/github-ae@latest/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69617,6 +71800,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69626,16 +71811,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was added to the enterprise. - */ "user/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69652,6 +71837,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69661,16 +71848,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to user accounts in an enterprise. - * @description A user account was removed from the enterprise. - */ "user/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69687,6 +71874,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69696,18 +71885,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/github-ae@latest/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/github-ae@latest/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69724,6 +71911,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69733,19 +71922,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/github-ae@latest/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69762,6 +71948,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69771,20 +71959,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/github-ae@latest/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/github-ae@latest/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69801,6 +71985,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69810,20 +71996,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/github-ae@latest/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/github-ae@latest/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69840,6 +72022,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69849,20 +72033,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/github-ae@latest/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/github-ae@latest/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69879,6 +72059,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69888,20 +72070,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/github-ae@latest/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/github-ae@latest/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69918,6 +72096,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69927,20 +72107,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/github-ae@latest/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/github-ae@latest/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69957,6 +72133,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69966,20 +72144,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/github-ae@latest/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/github-ae@latest/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/github-ae@latest/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69996,6 +72170,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -70005,7 +72181,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/packages/openapi-webhooks-types/types.d.ts b/packages/openapi-webhooks-types/types.d.ts index 824b479..c29ba36 100644 --- a/packages/openapi-webhooks-types/types.d.ts +++ b/packages/openapi-webhooks-types/types.d.ts @@ -3,2791 +3,6004 @@ * Do not make direct changes to the file. */ -/** OneOf type helpers */ -type Without = { [P in Exclude]?: never }; -type XOR = T | U extends object - ? (Without & U) | (Without & T) - : T | U; -type OneOf = T extends [infer Only] - ? Only - : T extends [infer A, infer B, ...infer Rest] - ? OneOf<[XOR, ...Rest]> - : never; - export type paths = Record; - export interface webhooks { "branch-protection-configuration-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were disabled for a repository. */ post: operations["branch-protection-configuration/disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-configuration-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. + * For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." + * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description All branch protections were enabled for a repository. */ post: operations["branch-protection-configuration/enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was created. */ post: operations["branch-protection-rule/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was deleted. */ post: operations["branch-protection-rule/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "branch-protection-rule-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. * @description A branch protection rule was edited. */ post: operations["branch-protection-rule/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run was completed, and a conclusion is available. */ post: operations["check-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A new check run was created. */ post: operations["check-run/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-requested-action": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/developers/apps/guides/creating-ci-tests-with-the-checks-api)." */ post: operations["check-run/requested-action"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-run-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. * - * For activity relating to check suites, use the `check-suite` event. + * For activity relating to check suites, use the `check-suite` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. */ post: operations["check-run/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description All check runs in a check suite have completed, and a conclusion is available. */ post: operations["check-suite/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/rest/checks/runs#create-a-check-run)" in the REST API documentation. */ post: operations["check-suite/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "check-suite-rerequested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/rest/checks/suites)" in the REST API documentation. * - * For activity relating to check runs, use the `check_run` event. + * For activity relating to check runs, use the `check_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. + * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. + * > [!NOTE] + * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/rest/checks/suites#create-a-check-suite)" in the REST API documentation. */ post: operations["check-suite/rerequested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-appeared-in-branch": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. */ post: operations["code-scanning-alert/appeared-in-branch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-closed-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone closed a code scanning alert. */ post: operations["code-scanning-alert/closed-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was created in a repository. */ post: operations["code-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A code scanning alert was fixed in a branch by a commit. */ post: operations["code-scanning-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description A previously fixed code scanning alert reappeared in a branch. */ post: operations["code-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "code-scanning-alert-reopened-by-user": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. * @description Someone reopened a code scanning alert. */ post: operations["code-scanning-alert/reopened-by-user"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "commit-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/rest/commits/comments)" in the REST API documentation. * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. + * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description Someone commented on a commit. */ post: operations["commit-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; create: { - /** - * This event occurs when a Git branch or tag is created. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is created. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ + * **Notes**: + * - This event will not occur when more than three tags are created at once. + * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. */ post: operations["create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a custom property. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description A new custom property was created. */ post: operations["custom-property/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a custom property. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description A custom property was deleted. */ post: operations["custom-property/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a custom property. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description A custom property was updated. */ post: operations["custom-property/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "custom-property-values-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to custom property values for a repository. * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties for a repository, see "[Custom properties](https://docs.github.com/rest/repos/custom-properties)" in the REST API documentation. + * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties for a repository, see "[Custom properties](https://docs.github.com/rest/repos/custom-properties)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. * @description The custom property values of a repository were updated. */ post: operations["custom-property-values/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; delete: { - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including + * branch and tag deletions, use the [`push`](#push) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ + * > [!NOTE] + * > This event will not occur when more than three tags are deleted at once. */ post: operations["delete"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. */ post: operations["dependabot-alert/auto-dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-auto-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. */ post: operations["dependabot-alert/auto-reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. */ post: operations["dependabot-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually closed. */ post: operations["dependabot-alert/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-fixed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change removed a vulnerability. */ post: operations["dependabot-alert/fixed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reintroduced": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. */ post: operations["dependabot-alert/reintroduced"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "dependabot-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to Dependabot alerts. * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. + * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for Dependabot alerts are currently in beta and subject to change. * @description A Dependabot alert was manually reopened. */ post: operations["dependabot-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was created. */ post: operations["deploy-key/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deploy-key-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/rest/deploy-keys)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deploy key was deleted. */ post: operations["deploy-key/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment status, use the `deployment_status` event. + * For activity relating to deployment status, use the `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment was created. */ post: operations["deployment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-protection-rule-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/rest/deployments/environments). * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment protection rule was requested for an environment. */ post: operations["deployment-protection-rule/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was approved. */ post: operations["deployment-review/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-rejected": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was rejected. */ post: operations["deployment-review/rejected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. + * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * @description A deployment review was requested. */ post: operations["deployment-review/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "deployment-status-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. * - * For activity relating to deployment creation, use the `deployment` event. + * For activity relating to deployment creation, use the `deployment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. + * > [!NOTE] + * > A webhook event is not fired for deployment statuses with an `inactive` state. * @description A new deployment status was created. */ post: operations["deployment-status/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-answered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was marked as the answer. */ post: operations["discussion/answered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-category-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The category of a discussion was changed. */ post: operations["discussion/category-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was closed. */ post: operations["discussion/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was created. */ post: operations["discussion-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was deleted. */ post: operations["discussion-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. + * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on a discussion was edited. */ post: operations["discussion-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was created. */ post: operations["discussion/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was deleted. */ post: operations["discussion/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description The title or body on a discussion was edited, or the category of the discussion was changed. */ post: operations["discussion/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was added to a discussion. */ post: operations["discussion/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was locked. */ post: operations["discussion/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was pinned. */ post: operations["discussion/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was reopened. */ post: operations["discussion/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was transferred to another repository. */ post: operations["discussion/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unanswered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A comment on the discussion was unmarked as the answer. */ post: operations["discussion/unanswered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A label was removed from a discussion. */ post: operations["discussion/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unlocked. */ post: operations["discussion/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "discussion-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. + * For activity relating to a comment on a discussion, use the `discussion_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. + * > [!NOTE] + * > Webhook events for GitHub Discussions are currently in beta and subject to change. * @description A discussion was unpinned. */ post: operations["discussion/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; fork: { - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/rest/repos/forks)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/rest/repos/forks)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["fork"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "github-app-authorization-revoked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. + * A GitHub App receives this webhook by default and cannot unsubscribe from this event. * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." + * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." * @description Someone revoked their authorization of a GitHub App. */ post: operations["github-app-authorization/revoked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; gollum: { - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/communities/documenting-your-project-with-wikis/about-wikis)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/communities/documenting-your-project-with-wikis/about-wikis)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["gollum"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description Someone installed a GitHub App on a user or organization account. */ post: operations["installation/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description Someone uninstalled a GitHub App from their user or organization account. */ post: operations["installation/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-new-permissions-accepted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description Someone granted new permissions to a GitHub App. */ post: operations["installation/new-permissions-accepted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description A GitHub App installation was granted access to one or more repositories. */ post: operations["installation-repositories/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-repositories-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description Access to one or more repositories was revoked for a GitHub App installation. */ post: operations["installation-repositories/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-suspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description Someone blocked access by a GitHub App to their user or organization account. */ post: operations["installation/suspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-target-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description Somebody renamed the user or organization account that a GitHub App is installed on. */ post: operations["installation-target/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "installation-unsuspend": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. + * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. */ post: operations["installation/unsuspend"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was created. */ post: operations["issue-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was deleted. */ post: operations["issue-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issue-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/rest/issues/comments)" in the REST API documentation. * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." + * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A comment on an issue or pull request was edited. */ post: operations["issue-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was assigned to a user. */ post: operations["issues/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was closed. */ post: operations["issues/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was deleted. */ post: operations["issues/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was removed from a milestone. */ post: operations["issues/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description The title or body on an issue was edited. */ post: operations["issues/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was added to an issue. */ post: operations["issues/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was added to a milestone. */ post: operations["issues/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. */ post: operations["issues/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-pinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/pinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A closed issue was reopened. */ post: operations["issues/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." */ post: operations["issues/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A user was unassigned from an issue. */ post: operations["issues/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description A label was removed from an issue. */ post: operations["issues/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["issues/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "issues-unpinned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. * - * For activity relating to a comment on an issue, use the `issue_comment` event. + * For activity relating to a comment on an issue, use the `issue_comment` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." */ post: operations["issues/unpinned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#label) or "[Labels](https://docs.github.com/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was created. */ post: operations["label/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#label) or "[Labels](https://docs.github.com/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label was deleted. */ post: operations["label/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "label-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#label) or "[Labels](https://docs.github.com/rest/issues/labels)" in the REST API documentation. * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. + * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A label's name, description, or color was changed. */ post: operations["label/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. * @description Someone cancelled a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. */ post: operations["marketplace-purchase/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. * @description Someone upgraded or downgraded a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. */ post: operations["marketplace-purchase/changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-pending-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. * @description Someone downgraded or cancelled a GitHub Marketplace plan. The new plan or cancellation will take effect at the end of the current billing cycle. When the change takes effect, the `changed` or `cancelled` event will be sent. */ post: operations["marketplace-purchase/pending-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-pending-change-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. * @description Someone cancelled a pending change to a GitHub Marketplace plan. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle. */ post: operations["marketplace-purchase/pending-change-cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "marketplace-purchase-purchased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. * @description Someone purchased a GitHub Marketplace plan. The change will take effect on the account immediately. */ post: operations["marketplace-purchase/purchased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A GitHub user accepted an invitation to a repository. */ post: operations["member/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description Permissions were changed for a collaborator on a repository. */ post: operations["member/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/rest/collaborators/collaborators)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A collaborator was removed from a repository. */ post: operations["member/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#team) or "[Team members](https://docs.github.com/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was added to a team. */ post: operations["membership/added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "membership-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#team) or "[Team members](https://docs.github.com/rest/teams/members)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization member was removed from a team. */ post: operations["membership/removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "merge-group-checks-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. * @description Status checks were requested for a merge group. This happens when a merge group is created or added to by the merge queue because a pull request was queued. * - * When you receive this event, you should perform checks on the head SHA and report status back using check runs or commit statuses. + * When you receive this event, you should perform checks on the head SHA and report status back using check runs or commit statuses. */ post: operations["merge-group/checks-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "merge-group-destroyed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. * @description The merge queue groups pull requests together to be merged. This event indicates that one of those merge groups was destroyed. This happens when a pull request is removed from the queue: any group containing that pull request is also destroyed. * - * When you receive this event, you may want to cancel any checks that are running on the head SHA to avoid wasting computing resources on a merge group that will not be used. + * When you receive this event, you may want to cancel any checks that are running on the head SHA to avoid wasting computing resources on a merge group that will not be used. */ post: operations["merge-group/destroyed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "meta-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a webhook itself. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. * @description The webhook was deleted. */ post: operations["meta/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was closed. */ post: operations["milestone/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was created. */ post: operations["milestone/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was deleted. */ post: operations["milestone/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was edited. */ post: operations["milestone/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "milestone-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. + * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. * @description A milestone was opened. */ post: operations["milestone/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "org-block-blocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/rest/orgs/blocking)" in the REST API documentation. * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. + * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. * @description A user was blocked from the organization. */ post: operations["org-block/blocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "org-block-unblocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/rest/orgs/blocking)" in the REST API documentation. * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. + * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. * @description A previously blocked user was unblocked from the organization. */ post: operations["org-block/unblocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description An organization was deleted. */ post: operations["organization/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member accepted an invitation to join an organization. */ post: operations["organization/member-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-invited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was invited to join the organization. */ post: operations["organization/member-invited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-member-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A member was removed from the organization. */ post: operations["organization/member-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "organization-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. + * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name of an organization was changed. */ post: operations["organization/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A package was published to a registry. */ post: operations["package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * @description A previously published package was updated. */ post: operations["package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "page-build": { - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/rest/pages)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/rest/pages)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. */ post: operations["page-build"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-approved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was approved. */ post: operations["personal-access-token-request/approved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was cancelled by the requester. */ post: operations["personal-access-token-request/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was created. */ post: operations["personal-access-token-request/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "personal-access-token-request-denied": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. + * > [!NOTE] + * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. * @description A fine-grained personal access token request was denied. */ post: operations["personal-access-token-request/denied"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; ping: { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ post: operations["ping"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note in a project (classic) was converted to an issue. */ post: operations["project-card/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card was added to a project (classic). */ post: operations["project-card/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was deleted. */ post: operations["project-card/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A note on a project (classic) was edited. */ post: operations["project-card/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-card-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. + * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A card on a project (classic) was moved to another column or to another position in its column. */ post: operations["project-card/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was added to a project (classic). */ post: operations["project-column/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was deleted from a project (classic). */ post: operations["project-column/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name of a column on a project (classic) was changed. */ post: operations["project-column/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-column-moved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. + * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A column was moved to a new position on a project (classic). */ post: operations["project-column/moved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was created. */ post: operations["project/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was deleted. */ post: operations["project/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description The name or description of a project (classic) was changed. */ post: operations["project/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "project-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. + * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. + * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. * @description A project (classic) was closed. */ post: operations["project/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was closed. */ post: operations["projects-v2/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was created. */ post: operations["projects-v2/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was deleted. */ post: operations["projects-v2/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The title, description, or README of a project in the organization was changed. */ post: operations["projects-v2/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-converted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A draft issue in an organization project was converted to an issue. */ post: operations["projects-v2-item/converted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was added to a project in the organization. */ post: operations["projects-v2-item/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An item was deleted from a project in the organization. */ post: operations["projects-v2-item/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. */ post: operations["projects-v2-item/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-reordered": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. */ post: operations["projects-v2-item/reordered"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-item-restored": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." */ post: operations["projects-v2-item/restored"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. + * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A project in the organization was reopened. */ post: operations["projects-v2/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-status-update-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." * - * For activity relating to a project, use the `projects_v2` event. + * For activity relating to a project, use the `projects_v2` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A status update was added to a project in the organization. */ post: operations["projects-v2-status-update/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-status-update-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." * - * For activity relating to a project, use the `projects_v2` event. + * For activity relating to a project, use the `projects_v2` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A status update was removed from a project in the organization. */ post: operations["projects-v2-status-update/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "projects-v2-status-update-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." * - * For activity relating to a project, use the `projects_v2` event. + * For activity relating to a project, use the `projects_v2` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). + * > [!NOTE] + * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). * @description A status update was edited on a project in the organization. */ post: operations["projects-v2-status-update/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; public: { - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. */ post: operations["public"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-assigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was assigned to a user. */ post: operations["pull-request/assigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-disabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-disabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-auto-merge-enabled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." */ post: operations["pull-request/auto-merge-enabled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-closed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. */ post: operations["pull-request/closed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-converted-to-draft": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/converted-to-draft"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-demilestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from a milestone. */ post: operations["pull-request/demilestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-dequeued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was removed from the merge queue. */ post: operations["pull-request/dequeued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. */ post: operations["pull-request/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-enqueued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to the merge queue. */ post: operations["pull-request/enqueued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-labeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was added to a pull request. */ post: operations["pull-request/labeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-locked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/locked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-milestoned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was added to a milestone. */ post: operations["pull-request/milestoned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-opened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request was created */ post: operations["pull-request/opened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-ready-for-review": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." */ post: operations["pull-request/ready-for-review"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously closed pull request was reopened. */ post: operations["pull-request/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was created. */ post: operations["pull-request-review-comment/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment on a pull request diff was deleted. */ post: operations["pull-request-review-comment/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-comment-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The content of a comment on a pull request diff was changed. */ post: operations["pull-request-review-comment/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-dismissed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was dismissed. */ post: operations["pull-request-review/dismissed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description The body comment on a pull request review was edited. */ post: operations["pull-request-review/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-request-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A request for review by a person or team was removed from a pull request. */ post: operations["pull-request/review-request-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." */ post: operations["pull-request/review-requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-submitted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/rest/pulls/reviews)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A review on a pull request was submitted. */ post: operations["pull-request-review/submitted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A comment thread on a pull request was marked as resolved. */ post: operations["pull-request-review-thread/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-review-thread-unresolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. + * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A previously resolved comment thread on a pull request was marked as unresolved. */ post: operations["pull-request-review-thread/unresolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-synchronize": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. */ post: operations["pull-request/synchronize"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unassigned": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A user was unassigned from a pull request. */ post: operations["pull-request/unassigned"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlabeled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description A label was removed from a pull request. */ post: operations["pull-request/unlabeled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "pull-request-unlocked": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. + * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." */ post: operations["pull-request/unlocked"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; push: { - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, + * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch + * and tag deletions, use the [`delete`](#delete) webhook event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ + * > [!NOTE] + * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. */ post: operations["push"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package was published to a registry. */ post: operations["registry-package/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "registry-package-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. + * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. + * > [!NOTE] + * > GitHub recommends that you use the newer `package` event instead. * @description A package that was previously published to a registry was updated. */ post: operations["registry-package/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. */ post: operations["release/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft release was deleted. */ post: operations["release/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." */ post: operations["release/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-prereleased": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. */ post: operations["release/prereleased"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release, pre-release, or draft of a release was published. */ post: operations["release/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-released": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release was published, or a pre-release was changed to a release. */ post: operations["release/released"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "release-unpublished": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. * @description A release or pre-release was unpublished. */ post: operations["release/unpublished"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. * @description A repository security advisory was published. */ post: operations["repository-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-advisory-reported": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. * @description A private vulnerability report was submitted. */ post: operations["repository-advisory/reported"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-archived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was archived. */ post: operations["repository/archived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was created. */ post: operations["repository/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. */ post: operations["repository/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-dispatch-sample.collected": { - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["repository-dispatch/sample.collected"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The topics, default branch, description, or homepage of a repository was changed. */ post: operations["repository/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-import": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** This event occurs when a repository is imported to GitHub. For more information, see "[Importing a repository with GitHub Importer](https://docs.github.com/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." For more information about the API to manage imports, see [the REST API documentation](https://docs.github.com/rest/migrations/source-imports). */ post: operations["repository-import"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-privatized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `private`. */ post: operations["repository/privatized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-publicized": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The visibility of a repository was changed to `public`. */ post: operations["repository/publicized"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-renamed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description The name of a repository was changed. */ post: operations["repository/renamed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was created. */ post: operations["repository-ruleset/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was deleted. */ post: operations["repository-ruleset/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-ruleset-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." + * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." + * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. * @description A repository ruleset was edited. */ post: operations["repository-ruleset/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-transferred": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. */ post: operations["repository/transferred"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-unarchived": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description A previously archived repository was unarchived. */ post: operations["repository/unarchived"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-create": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was created. */ post: operations["repository-vulnerability-alert/create"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-dismiss": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was dismissed. */ post: operations["repository-vulnerability-alert/dismiss"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-reopen": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A previously dismissed or resolved repository vulnerability alert was reopened. */ post: operations["repository-vulnerability-alert/reopen"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "repository-vulnerability-alert-resolve": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a security vulnerability alert in a repository. * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. + * > [!WARNING] + * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. * @description A repository vulnerability alert was marked as resolved. */ post: operations["repository-vulnerability-alert/resolve"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was created. */ post: operations["secret-scanning-alert/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-location-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. + * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. + * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. */ post: operations["secret-scanning-alert-location/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-reopened": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A previously closed secret scanning alert was reopened. */ post: operations["secret-scanning-alert/reopened"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-resolved": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was closed. */ post: operations["secret-scanning-alert/resolved"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "secret-scanning-alert-validated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. + * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. * @description A secret scanning alert was validated. */ post: operations["secret-scanning-alert/validated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-published": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A security advisory was published to the GitHub community. */ post: operations["security-advisory/published"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-updated": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description The metadata or description of a security advisory was changed. */ post: operations["security-advisory/updated"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-advisory-withdrawn": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#securityadvisory). * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." * @description A previously published security advisory was withdrawn. */ post: operations["security-advisory/withdrawn"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "security-and-analysis": { - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/code-security/getting-started/github-security-features)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/code-security/getting-started/github-security-features)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. */ post: operations["security-and-analysis"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-cancelled": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsorship was cancelled and the last billing cycle has ended. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/cancelled"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. */ post: operations["sponsorship/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. */ post: operations["sponsorship/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-cancellation": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. + * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. */ post: operations["sponsorship/pending-cancellation"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-pending-tier-change": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. */ post: operations["sponsorship/pending-tier-change"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sponsorship-tier-changed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." + * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. */ post: operations["sponsorship/tier-changed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone starred a repository. */ post: operations["star/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "star-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/rest/activity/starring)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone unstarred the repository. */ post: operations["star/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; status: { - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/rest/commits/statuses)" in the REST API documentation. + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/rest/commits/statuses)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. */ post: operations["status"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-parent-issue-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A parent issue was added to an issue. */ post: operations["sub-issues/parent-issue-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-parent-issue-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A parent issue was removed from an issue. */ post: operations["sub-issues/parent-issue-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-sub-issue-added": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A sub-issue was added to an issue. */ post: operations["sub-issues/sub-issue-added"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "sub-issues-sub-issue-removed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to sub-issues. * - * For activity relating to issues more generally, use the `issues` event instead. + * For activity relating to issues more generally, use the `issues` event instead. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. * @description A sub-issue was removed from an issue. */ post: operations["sub-issues/sub-issue-removed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-add": { - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a team is added to a repository. + * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." * - * For activity relating to teams, see the `teams` event. + * For activity relating to teams, see the `teams` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. */ post: operations["team-add"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-added-to-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was granted access to a repository. */ post: operations["team/added-to-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-created": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was created. */ post: operations["team/created"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-deleted": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team was deleted. */ post: operations["team/deleted"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-edited": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description The name, description, or visibility of a team was changed. */ post: operations["team/edited"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "team-removed-from-repository": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." + * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. * @description A team's access to a repository was removed. */ post: operations["team/removed-from-repository"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "watch-started": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/rest/activity/watching)" in the REST API documentation. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. * @description Someone started watching the repository. */ post: operations["watch/started"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-dispatch": { - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/actions/managing-workflow-runs/manually-running-a-workflow)." + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; + /** This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/actions/managing-workflow-runs/manually-running-a-workflow)." * - * For activity relating to workflow runs, use the `workflow_run` event. + * For activity relating to workflow runs, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ + * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. */ post: operations["workflow-dispatch"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. */ post: operations["workflow-job/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run started processing on a runner. */ post: operations["workflow-job/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-queued": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created. */ post: operations["workflow-job/queued"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-job-waiting": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. + * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A job in a workflow run was created and is waiting for approvals. */ post: operations["workflow-job/waiting"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-completed": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. */ post: operations["workflow-run/completed"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-in-progress": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run started processing on a runner. */ post: operations["workflow-run/in-progress"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; "workflow-run-requested": { + parameters: { + query?: never; + header?: never; + path?: never; + cookie?: never; + }; + get?: never; + put?: never; /** * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/rest/actions/workflow-runs)" in the REST API documentation. * - * For activity relating to a job in a workflow run, use the `workflow_job` event. + * For activity relating to a job in a workflow run, use the `workflow_job` event. * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. + * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. * @description A workflow run was triggered. */ post: operations["workflow-run/requested"]; + delete?: never; + options?: never; + head?: never; + patch?: never; + trace?: never; }; } - export interface components { schemas: { /** branch protection configuration disabled event */ @@ -2802,8 +6015,8 @@ export interface components { /** * Simple Installation * @description The GitHub App installation. Webhook payloads contain the `installation` property when the event is configured - * for and sent to a GitHub App. For more information, - * see "[Using webhooks with GitHub Apps](https://docs.github.com/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." + * for and sent to a GitHub App. For more information, + * see "[Using webhooks with GitHub Apps](https://docs.github.com/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps)." */ "simple-installation": { /** @description The ID of the installation. */ @@ -2814,7 +6027,7 @@ export interface components { /** * Organization Simple * @description A GitHub organization. Webhook payloads contain the `organization` property when the webhook is configured for an - * organization, or when the event occurs from activity in a repository owned by an organization. + * organization, or when the event occurs from activity in a repository owned by an organization. */ "organization-simple-webhooks": { login: string; @@ -2836,7 +6049,7 @@ export interface components { /** * Repository * @description The repository on GitHub where the event occurred. Webhook payloads contain the `repository` property - * when the event occurs from activity in a repository. + * when the event occurs from activity in a repository. */ "repository-webhooks": { /** @@ -3105,34 +6318,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3170,34 +6383,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -3534,9 +6747,9 @@ export interface components { /** * @description The set of permissions for the GitHub app * @example { - * "issues": "read", - * "deployments": "write" - * } + * "issues": "read", + * "deployments": "write" + * } */ permissions: { issues?: string; @@ -3544,7 +6757,8 @@ export interface components { metadata?: string; contents?: string; deployments?: string; - [key: string]: string | undefined; + } & { + [key: string]: string; }; /** @description The list of events for the GitHub app */ events: string[]; @@ -5587,13 +8801,11 @@ export interface components { /** @description Whether the property is required. */ required?: boolean; /** @description Default value of the property */ - default_value?: string | string[] | null | unknown[]; + default_value?: (null | unknown[]) & (string | string[]); /** @description Short description of the property */ description?: string | null; - /** - * @description An ordered list of the allowed values of the property. - * The property can have up to 200 allowed values. - */ + /** @description An ordered list of the allowed values of the property. + * The property can have up to 200 allowed values. */ allowed_values?: string[] | null; /** * @description Who can edit the values of the property @@ -5643,7 +8855,7 @@ export interface components { /** @description The name of the property */ property_name: string; /** @description The value assigned to the property */ - value: string | string[] | null | unknown[]; + value: (null | unknown[]) & (string | string[]); }; /** delete event */ "webhook-delete": { @@ -5676,10 +8888,10 @@ export interface components { * @description The state of the Dependabot alert. * @enum {string} */ - state: "auto_dismissed" | "dismissed" | "fixed" | "open"; + readonly state: "auto_dismissed" | "dismissed" | "fixed" | "open"; /** @description Details for the vulnerable dependency. */ - dependency: { - readonly package?: components["schemas"]["dependabot-alert-package"]; + readonly dependency: { + package?: components["schemas"]["dependabot-alert-package"]; /** @description The full path to the dependency manifest file, relative to the root of the repository. */ readonly manifest_path?: string; /** @@ -5713,16 +8925,16 @@ export interface components { auto_dismissed_at?: components["schemas"]["alert-auto-dismissed-at"]; }; /** @description The security alert number. */ - readonly "alert-number": number; + "alert-number": number; /** @description Details for the vulnerable package. */ - readonly "dependabot-alert-package": { + "dependabot-alert-package": { /** @description The package's language or package management ecosystem. */ readonly ecosystem: string; /** @description The unique package name within its ecosystem. */ readonly name: string; }; /** @description Details for the GitHub Security Advisory. */ - readonly "dependabot-alert-security-advisory": { + "dependabot-alert-security-advisory": { /** @description The unique GitHub Security Advisory ID assigned to the advisory. */ readonly ghsa_id: string; /** @description The unique CVE ID assigned to the advisory. */ @@ -5732,7 +8944,7 @@ export interface components { /** @description A long-form Markdown-supported description of the advisory. */ readonly description: string; /** @description Vulnerable version range information for the advisory. */ - readonly vulnerabilities: readonly components["schemas"]["dependabot-alert-security-vulnerability"][]; + readonly vulnerabilities: components["schemas"]["dependabot-alert-security-vulnerability"][]; /** * @description The severity of the advisory. * @enum {string} @@ -5746,14 +8958,14 @@ export interface components { readonly vector_string: string | null; }; /** @description Details for the advisory pertaining to Common Weakness Enumeration. */ - readonly cwes: readonly { + readonly cwes: { /** @description The unique CWE ID. */ readonly cwe_id: string; /** @description The short, plain text name of the CWE. */ readonly name: string; }[]; /** @description Values that identify this advisory among security information sources. */ - readonly identifiers: readonly { + readonly identifiers: { /** * @description The type of advisory identifier. * @enum {string} @@ -5763,7 +8975,7 @@ export interface components { readonly value: string; }[]; /** @description Links to additional advisory information. */ - readonly references: readonly { + readonly references: { /** * Format: uri * @description The URL of the reference. @@ -5787,8 +8999,8 @@ export interface components { readonly withdrawn_at: string | null; }; /** @description Details pertaining to one vulnerable version range for the advisory. */ - readonly "dependabot-alert-security-vulnerability": { - readonly package: components["schemas"]["dependabot-alert-package"]; + "dependabot-alert-security-vulnerability": { + package: components["schemas"]["dependabot-alert-package"]; /** * @description The severity of the vulnerability. * @enum {string} @@ -5806,37 +9018,37 @@ export interface components { * Format: uri * @description The REST API URL of the alert resource. */ - readonly "alert-url": string; + "alert-url": string; /** * Format: uri * @description The GitHub URL of the alert resource. */ - readonly "alert-html-url": string; + "alert-html-url": string; /** * Format: date-time * @description The time that the alert was created in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-created-at": string; + "alert-created-at": string; /** * Format: date-time * @description The time that the alert was last updated in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-updated-at": string; + "alert-updated-at": string; /** * Format: date-time * @description The time that the alert was dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-dismissed-at": string | null; + "alert-dismissed-at": string | null; /** * Format: date-time * @description The time that the alert was no longer detected and was considered fixed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-fixed-at": string | null; + "alert-fixed-at": string | null; /** * Format: date-time * @description The time that the alert was auto-dismissed in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`. */ - readonly "alert-auto-dismissed-at": string | null; + "alert-auto-dismissed-at": string | null; /** Dependabot alert auto-reopened event */ "webhook-dependabot-alert-auto-reopened": { /** @enum {string} */ @@ -6539,14 +9751,11 @@ export interface components { ref: string; /** @description Parameter to specify a task to execute */ task: string; - payload: OneOf< - [ - { + payload: + | { [key: string]: unknown; - }, - string, - ] - >; + } + | string; original_environment?: string; /** @description Name for the target deployment environment. */ environment: string; @@ -8317,7 +11526,8 @@ export interface components { id: number; node_id: string; original_environment: string; - payload: string | Record | null; + payload: (null | Record) & + (string | Record); /** * App * @description GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub. @@ -9254,8 +12464,8 @@ export interface components { repository_url: string; /** * @description The current state of the discussion. - * `converting` means that the discussion is being converted from an issue. - * `transferring` means that the discussion is being transferred from another repository. + * `converting` means that the discussion is being converted from an issue. + * `transferring` means that the discussion is being transferred from another repository. * @enum {string} */ state: "open" | "closed" | "locked" | "converting" | "transferring"; @@ -9842,7 +13052,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -10034,11 +13244,15 @@ export interface components { /** @description The ID of the installation. */ id: number; account: - | null | ( - | components["schemas"]["simple-user"] - | components["schemas"]["enterprise"] - ); + | null + | ( + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"] + ) + ) + | components["schemas"]["simple-user"] + | components["schemas"]["enterprise"]; /** * @description Describe whether all repositories have been selected or there's a selection involved * @enum {string} @@ -10101,11 +13315,11 @@ export interface components { * App Permissions * @description The permissions granted to the user access token. * @example { - * "contents": "read", - * "issues": "read", - * "deployments": "write", - * "single_file": "read" - * } + * "contents": "read", + * "issues": "read", + * "deployments": "write", + * "single_file": "read" + * } */ "app-permissions": { /** @@ -17173,7 +20387,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -19337,7 +22551,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -20174,12 +23388,10 @@ export interface components { /** @enum {string} */ action: "added"; changes?: { - /** - * @description This field is included for legacy purposes; use the `role_name` field instead. The `maintain` - * role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role - * assigned to the collaborator, use the `role_name` field instead, which will provide the full - * role name, including custom roles. - */ + /** @description This field is included for legacy purposes; use the `role_name` field instead. The `maintain` + * role is mapped to `write` and the `triage` role is mapped to `read`. To determine the role + * assigned to the collaborator, use the `role_name` field instead, which will provide the full + * role name, including custom roles. */ permission?: { /** @enum {string} */ to: "write" | "admin" | "read"; @@ -20406,6 +23618,7 @@ export interface components { /** * Merge Group * @description A group of pull requests that the merge queue has grouped together to be merged. + * */ "merge-group": { /** @description The SHA of the merge group. */ @@ -21163,19 +24376,16 @@ export interface components { | { id?: number | string; name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -22338,42 +25548,37 @@ export interface components { "webhook-projects-v2-item-edited": { /** @enum {string} */ action: "edited"; - /** - * @description The changes made to the item may involve modifications in the item's fields and draft issue body. - * It includes altered values for text, number, date, single select, and iteration fields, along with the GraphQL node ID of the changed field. - */ - changes?: OneOf< - [ - { + /** @description The changes made to the item may involve modifications in the item's fields and draft issue body. + * It includes altered values for text, number, date, single select, and iteration fields, along with the GraphQL node ID of the changed field. */ + changes?: + | { field_value: { field_node_id?: string; field_type?: string; field_name?: string; project_number?: number; - from?: - | string - | number - | components["schemas"]["projects-v2-single-select-option"] - | components["schemas"]["projects-v2-iteration-setting"] - | null - | Record; - to?: - | string - | number - | components["schemas"]["projects-v2-single-select-option"] - | components["schemas"]["projects-v2-iteration-setting"] - | null - | Record; + from?: (null | Record) & + ( + | string + | number + | components["schemas"]["projects-v2-single-select-option"] + | components["schemas"]["projects-v2-iteration-setting"] + ); + to?: (null | Record) & + ( + | string + | number + | components["schemas"]["projects-v2-single-select-option"] + | components["schemas"]["projects-v2-iteration-setting"] + ); }; - }, - { + } + | { body: { from?: string | null; to?: string | null; }; - }, - ] - >; + }; installation?: components["schemas"]["simple-installation"]; organization: components["schemas"]["organization-simple-webhooks"]; projects_v2_item: components["schemas"]["projects-v2-item"]; @@ -22882,17 +26087,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -22959,7 +26164,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -22967,9 +26172,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -22979,8 +26184,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23229,17 +26434,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -23306,7 +26511,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -23314,9 +26519,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -23326,8 +26531,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -23550,9 +26755,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -23587,8 +26791,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -23638,9 +26842,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -24104,17 +27307,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24181,7 +27384,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24189,9 +27392,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24201,8 +27404,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24451,17 +27654,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -24528,7 +27731,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -24536,9 +27739,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -24548,8 +27751,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -24772,9 +27975,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -24809,8 +28011,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -24860,9 +28062,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -25325,17 +28526,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25402,7 +28603,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25410,9 +28611,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25422,8 +28623,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25669,17 +28870,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -25746,7 +28947,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -25754,9 +28955,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -25766,8 +28967,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -25990,9 +29191,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -26027,8 +29227,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -26078,9 +29278,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -26219,31 +29418,31 @@ export interface components { delete_branch_on_merge?: boolean; /** * @description The default value for a merge commit message. - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., "Merge pull request #123 from branch-name"). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a squash merge commit message: - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26618,17 +29817,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -26695,7 +29894,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -26703,17 +29902,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -26962,17 +30161,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27039,7 +30238,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27047,17 +30246,17 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -27280,9 +30479,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -27317,8 +30515,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -27368,9 +30566,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -27829,17 +31026,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -27906,7 +31103,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -27914,9 +31111,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -27926,8 +31123,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28176,17 +31373,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -28253,7 +31450,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -28261,9 +31458,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -28273,8 +31470,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -28497,9 +31694,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -28534,8 +31730,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -28585,9 +31781,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -29080,17 +32275,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29157,7 +32352,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29165,9 +32360,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29177,8 +32372,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29427,17 +32622,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -29504,7 +32699,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -29512,9 +32707,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -29524,8 +32719,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -29748,9 +32943,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -29785,8 +32979,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -29836,9 +33030,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -30301,17 +33494,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30378,7 +33571,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30386,9 +33579,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30398,8 +33591,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30648,17 +33841,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -30725,7 +33918,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -30733,9 +33926,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -30745,8 +33938,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -30969,9 +34162,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -31006,8 +34198,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -31057,9 +34249,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -31521,17 +34712,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31598,7 +34789,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31606,9 +34797,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31618,8 +34809,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -31868,17 +35059,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -31945,7 +35136,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -31953,9 +35144,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -31965,8 +35156,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -32189,9 +35380,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -32226,8 +35416,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -32277,9 +35467,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -32936,17 +36125,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33013,7 +36202,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33021,9 +36210,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33033,8 +36222,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33276,17 +36465,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -33353,7 +36542,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -33361,9 +36550,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -33373,8 +36562,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -33552,9 +36741,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -33589,8 +36777,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -33640,9 +36828,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -34096,17 +37283,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -34173,7 +37360,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -34181,9 +37368,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -34193,8 +37380,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34436,17 +37623,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -34513,7 +37700,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -34521,9 +37708,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -34533,8 +37720,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -34712,9 +37899,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -34749,8 +37935,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -34800,9 +37986,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -35411,17 +38596,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35488,7 +38673,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35496,9 +38681,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -35508,8 +38693,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -35751,17 +38936,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -35828,7 +39013,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -35836,9 +39021,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -35848,8 +39033,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36027,9 +39212,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -36064,8 +39248,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -36115,9 +39299,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -36571,17 +39754,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36648,7 +39831,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36656,9 +39839,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -36668,8 +39851,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -36911,17 +40094,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -36988,7 +40171,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -36996,9 +40179,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -37008,8 +40191,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -37187,9 +40370,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -37224,8 +40406,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -37275,9 +40457,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -37874,7 +41055,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38165,7 +41346,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -38337,9 +41518,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -38374,8 +41554,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -38425,9 +41605,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -38616,9 +41795,8 @@ export interface components { } | null; }; /** pull_request review_request_removed event */ - "webhook-pull-request-review-request-removed": OneOf< - [ - { + "webhook-pull-request-review-request-removed": + | { /** @enum {string} */ action: "review_request_removed"; installation?: components["schemas"]["simple-installation"]; @@ -38968,17 +42146,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39045,7 +42223,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39308,17 +42486,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -39385,7 +42563,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -39393,9 +42571,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -39405,8 +42583,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -39629,9 +42807,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -39666,8 +42843,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -39717,9 +42894,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -39867,8 +43043,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_request_removed"; installation?: components["schemas"]["simple-installation"]; @@ -40218,17 +43394,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40295,7 +43471,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40303,9 +43479,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40315,8 +43491,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40565,17 +43741,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -40642,7 +43818,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -40650,9 +43826,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -40662,8 +43838,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -40886,9 +44062,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -40923,8 +44098,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -40974,9 +44149,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -41142,13 +44316,10 @@ export interface components { url: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request review_requested event */ - "webhook-pull-request-review-requested": OneOf< - [ - { + "webhook-pull-request-review-requested": + | { /** @enum {string} */ action: "review_requested"; installation?: components["schemas"]["simple-installation"]; @@ -41498,17 +44669,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41575,7 +44746,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41583,9 +44754,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41595,8 +44766,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -41845,17 +45016,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -41922,7 +45093,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -41930,9 +45101,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -41942,8 +45113,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -42166,9 +45337,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -42203,8 +45373,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -42254,9 +45424,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -42404,8 +45573,8 @@ export interface components { url?: string; } | null; sender: components["schemas"]["simple-user-webhooks"]; - }, - { + } + | { /** @enum {string} */ action: "review_requested"; installation?: components["schemas"]["simple-installation"]; @@ -42755,17 +45924,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -42832,7 +46001,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -42840,9 +46009,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -42852,8 +46021,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -43102,17 +46271,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -43179,7 +46348,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -43187,9 +46356,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -43199,8 +46368,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -43423,9 +46592,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -43460,8 +46628,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -43511,9 +46679,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -43679,9 +46846,7 @@ export interface components { url?: string; }; sender: components["schemas"]["simple-user-webhooks"]; - }, - ] - >; + }; /** pull_request_review submitted event */ "webhook-pull-request-review-submitted": { /** @enum {string} */ @@ -44030,17 +47195,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44107,7 +47272,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44115,9 +47280,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44127,8 +47292,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -44370,17 +47535,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -44447,7 +47612,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -44455,9 +47620,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -44467,8 +47632,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -44646,9 +47811,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -44683,8 +47847,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -44734,9 +47898,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -45251,7 +48414,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45549,7 +48712,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -45723,9 +48886,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -45760,8 +48922,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -45811,9 +48973,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -46480,7 +49641,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46778,7 +49939,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -46952,9 +50113,8 @@ export interface components { number: number; /** Format: uri */ patch_url: string; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -46989,8 +50149,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -47040,9 +50200,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -47653,17 +50812,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -47730,7 +50889,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -47738,9 +50897,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -47750,8 +50909,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48070,7 +51229,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48078,9 +51237,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48090,8 +51249,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -48314,9 +51473,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -48351,8 +51509,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -48402,9 +51560,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -48867,17 +52024,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -48944,7 +52101,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -48952,9 +52109,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -48964,8 +52121,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -49214,17 +52371,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -49291,7 +52448,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -49299,9 +52456,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -49311,8 +52468,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -49535,9 +52692,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -49572,8 +52728,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -49623,9 +52779,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -50088,17 +53243,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -50165,7 +53320,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -50173,9 +53328,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -50185,8 +53340,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -50505,7 +53660,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -50513,9 +53668,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -50525,8 +53680,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -50749,9 +53904,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -50786,8 +53940,8 @@ export interface components { type?: "Bot" | "User" | "Organization" | "Mannequin"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description: string | null; @@ -50837,9 +53991,8 @@ export interface components { * @description URL for the team */ url: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -51301,17 +54454,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -51378,7 +54531,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -51386,9 +54539,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -51398,8 +54551,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -51648,17 +54801,17 @@ export interface components { /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; @@ -51725,7 +54878,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -51733,9 +54886,9 @@ export interface components { /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: @@ -51745,8 +54898,8 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; @@ -51969,9 +55122,8 @@ export interface components { /** Format: uri */ patch_url: string; rebaseable?: boolean | null; - requested_reviewers: OneOf< - [ - { + requested_reviewers: ( + | ({ /** Format: uri */ avatar_url?: string; deleted?: boolean; @@ -52006,8 +55158,8 @@ export interface components { type?: "Bot" | "User" | "Organization"; /** Format: uri */ url?: string; - } | null, - { + } | null) + | { deleted?: boolean; /** @description Description of the team */ description?: string | null; @@ -52057,9 +55209,8 @@ export interface components { * @description URL for the team */ url?: string; - }, - ] - >[]; + } + )[]; requested_teams: { deleted?: boolean; /** @description Description of the team */ @@ -52518,7 +55669,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -52640,19 +55791,23 @@ export interface components { name?: string; version?: string; npm_user?: string; - author?: string | Record | null; - bugs?: string | Record | null; + author?: (null | Record) & + (string | Record); + bugs?: (null | Record) & + (string | Record); dependencies?: Record; dev_dependencies?: Record; peer_dependencies?: Record; optional_dependencies?: Record; description?: string; - dist?: string | Record | null; + dist?: (null | Record) & + (string | Record); git_head?: string; homepage?: string; license?: string; main?: string; - repository?: string | Record | null; + repository?: (null | Record) & + (string | Record); scripts?: Record; id?: string; node_version?: string; @@ -52665,7 +55820,8 @@ export interface components { files?: string[]; bin?: Record; man?: Record; - directories?: string | Record | null; + directories?: (null | Record) & + (string | Record); os?: string[]; cpu?: string[]; readme?: string; @@ -52677,21 +55833,19 @@ export interface components { } | null; nuget_metadata?: | { - id?: string | Record | number | null; + id?: (null | Record) & + (string | Record | number); name?: string; - value?: OneOf< - [ - boolean, - string, - number, - { + value?: + | boolean + | string + | number + | { url?: string; branch?: string; commit?: string; type?: string; - }, - ] - >; + }; }[] | null; package_files: { @@ -53433,19 +56587,19 @@ export interface components { /** @description A repository security advisory. */ "repository-advisory": { /** @description The GitHub Security Advisory ID. */ - ghsa_id: string; + readonly ghsa_id: string; /** @description The Common Vulnerabilities and Exposures (CVE) ID. */ cve_id: string | null; /** * Format: uri * @description The API URL for the advisory. */ - url: string; + readonly url: string; /** * Format: uri * @description The URL for the advisory. */ - html_url: string; + readonly html_url: string; /** @description A short summary of the advisory. */ summary: string; /** @description A detailed description of what the advisory entails. */ @@ -53456,10 +56610,10 @@ export interface components { */ severity: "critical" | "high" | "medium" | "low" | null; /** @description The author of the advisory. */ - author: null; + readonly author: null & components["schemas"]["simple-user"]; /** @description The publisher of the advisory. */ - publisher: null; - identifiers: readonly { + readonly publisher: null & components["schemas"]["simple-user"]; + readonly identifiers: { /** * @description The type of identifier. * @enum {string} @@ -53477,28 +56631,28 @@ export interface components { * Format: date-time * @description The date and time of when the advisory was created, in ISO 8601 format. */ - created_at: string | null; + readonly created_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was last updated, in ISO 8601 format. */ - updated_at: string | null; + readonly updated_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was published, in ISO 8601 format. */ - published_at: string | null; + readonly published_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was closed, in ISO 8601 format. */ - closed_at: string | null; + readonly closed_at: string | null; /** * Format: date-time * @description The date and time of when the advisory was withdrawn, in ISO 8601 format. */ - withdrawn_at: string | null; - submission: { + readonly withdrawn_at: string | null; + readonly submission: { /** @description Whether a private vulnerability report was accepted by the repository's administrators. */ readonly accepted: boolean; } | null; @@ -53509,14 +56663,14 @@ export interface components { /** @description The CVSS vector. */ vector_string: string | null; /** @description The CVSS score. */ - score: number | null; + readonly score: number | null; } | null; - cwes: - | readonly { + readonly cwes: + | { /** @description The Common Weakness Enumeration (CWE) identifier. */ cwe_id: string; /** @description The name of the CWE. */ - name: string; + readonly name: string; }[] | null; /** @description A list of only the CWE IDs. */ @@ -53528,15 +56682,15 @@ export interface components { type?: components["schemas"]["security-advisory-credit-types"]; }[] | null; - credits_detailed: - | readonly components["schemas"]["repository-advisory-credit"][] + readonly credits_detailed: + | components["schemas"]["repository-advisory-credit"][] | null; /** @description A list of users that collaborate on the advisory. */ collaborating_users: components["schemas"]["simple-user"][] | null; /** @description A list of teams that collaborate on the advisory. */ collaborating_teams: components["schemas"]["team"][] | null; /** @description A temporary private fork of the advisory's repository for collaborating on a fix. */ - private_fork: null; + readonly private_fork: null & components["schemas"]["simple-repository"]; }; /** @description A product affected by the vulnerability detailed in a repository security advisory. */ "repository-advisory-vulnerability": { @@ -53909,8 +57063,8 @@ export interface components { /** * @description The target of the ruleset * - * > [!NOTE] - * > The `push` target is in beta and is subject to change. + * > [!NOTE] + * > The `push` target is in beta and is subject to change. * @enum {string} */ target?: "branch" | "tag" | "push"; @@ -53926,7 +57080,7 @@ export interface components { bypass_actors?: components["schemas"]["repository-ruleset-bypass-actor"][]; /** * @description The bypass type of the user making the API request for this ruleset. This field is only returned when - * querying the repository-level endpoint. + * querying the repository-level endpoint. * @enum {string} */ current_user_can_bypass?: "always" | "pull_requests_only" | "never"; @@ -53942,11 +57096,15 @@ export interface components { }; }; conditions?: - | null | ( - | components["schemas"]["repository-ruleset-conditions"] - | components["schemas"]["org-ruleset-conditions"] - ); + | null + | ( + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"] + ) + ) + | components["schemas"]["repository-ruleset-conditions"] + | components["schemas"]["org-ruleset-conditions"]; rules?: components["schemas"]["repository-rule"][]; /** Format: date-time */ created_at?: string; @@ -53963,7 +57121,8 @@ export interface components { * @description An actor that can bypass rules in a ruleset */ "repository-ruleset-bypass-actor": { - /** @description The ID of the actor that can bypass a ruleset. If `actor_type` is `OrganizationAdmin`, this should be `1`. If `actor_type` is `DeployKey`, this should be null. `OrganizationAdmin` is not applicable for personal repositories. */ + /** @description The ID of the actor that can bypass a ruleset. If `actor_type` is `OrganizationAdmin`, this should be `1`. If `actor_type` is `DeployKey`, this should be null. `OrganizationAdmin` is not applicable for personal repositories. + * */ actor_id?: number | null; /** * @description The type of actor that can bypass a ruleset. @@ -53999,6 +57158,7 @@ export interface components { /** * Organization ruleset conditions * @description Conditions for an organization ruleset. The conditions object should contain both `repository_name` and `ref_name` properties or both `repository_id` and `ref_name` properties. + * */ "org-ruleset-conditions": | (components["schemas"]["repository-ruleset-conditions"] & @@ -54831,10 +57991,8 @@ export interface components { resolution_comment?: string | null; /** @description The type of secret that secret scanning detected. */ secret_type?: string; - /** - * @description User-friendly name for the detected secret, matching the `secret_type`. - * For a list of built-in patterns, see "[Supported secret scanning patterns](https://docs.github.com/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." - */ + /** @description User-friendly name for the detected secret, matching the `secret_type`. + * For a list of built-in patterns, see "[Supported secret scanning patterns](https://docs.github.com/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." */ secret_type_display_name?: string; /** * @description The token status as of the latest validity check. @@ -55304,34 +58462,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -55547,34 +58705,34 @@ export interface components { /** * @description The default value for a squash merge commit title: * - * - `PR_TITLE` - default to the pull request's title. - * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + * - `PR_TITLE` - default to the pull request's title. + * - `COMMIT_OR_PR_TITLE` - default to the commit's title (if only one commit) or the pull request's title (when more than one commit). * @enum {string} */ squash_merge_commit_title?: "PR_TITLE" | "COMMIT_OR_PR_TITLE"; /** * @description The default value for a squash merge commit message: * - * - `PR_BODY` - default to the pull request's body. - * - `COMMIT_MESSAGES` - default to the branch's commit messages. - * - `BLANK` - default to a blank commit message. + * - `PR_BODY` - default to the pull request's body. + * - `COMMIT_MESSAGES` - default to the branch's commit messages. + * - `BLANK` - default to a blank commit message. * @enum {string} */ squash_merge_commit_message?: "PR_BODY" | "COMMIT_MESSAGES" | "BLANK"; /** * @description The default value for a merge commit title. * - * - `PR_TITLE` - default to the pull request's title. - * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + * - `PR_TITLE` - default to the pull request's title. + * - `MERGE_MESSAGE` - default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). * @enum {string} */ merge_commit_title?: "PR_TITLE" | "MERGE_MESSAGE"; /** * @description The default value for a merge commit message. * - * - `PR_TITLE` - default to the pull request's title. - * - `PR_BODY` - default to the pull request's body. - * - `BLANK` - default to a blank commit message. + * - `PR_TITLE` - default to the pull request's title. + * - `PR_BODY` - default to the pull request's body. + * - `BLANK` - default to a blank commit message. * @enum {string} */ merge_commit_message?: "PR_BODY" | "PR_TITLE" | "BLANK"; @@ -56075,10 +59233,9 @@ export interface components { body?: string | null; user: null | components["schemas"]["simple-user"]; /** @description Labels to associate with this issue; pass one or more label names to replace the set of labels on this issue; send an empty array to clear all labels from the issue; note that the labels are silently dropped for users without push access to the repository */ - labels: OneOf< - [ - string, - { + labels: ( + | string + | { /** Format: int64 */ id?: number; node_id?: string; @@ -56088,9 +59245,8 @@ export interface components { description?: string | null; color?: string | null; default?: boolean; - }, - ] - >[]; + } + )[]; assignee: null | components["schemas"]["simple-user"]; assignees?: components["schemas"]["simple-user"][] | null; milestone: null | components["schemas"]["milestone"]; @@ -56477,7 +59633,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -56728,7 +59884,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -56979,7 +60135,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -57261,7 +60417,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -57512,7 +60668,7 @@ export interface components { public?: boolean; /** Format: uri-template */ pulls_url: string; - pushed_at: number | string | null; + pushed_at: null | number | string; /** Format: uri-template */ releases_url: string; role_name?: string | null; @@ -59285,22 +62441,11 @@ export interface components { headers: never; pathItems: never; } - export type $defs = Record; - -export type external = Record; - export interface operations { - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were disabled for a repository. - */ "branch-protection-configuration/disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59317,6 +62462,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59326,20 +62473,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a change to branch protection configurations for a repository. - * For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - * For information about using the APIs to manage branch protection rules, see "[Branch protection rule](https://docs.github.com/graphql/reference/objects#branchprotectionrule)" in the GraphQL documentation or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description All branch protections were enabled for a repository. - */ "branch-protection-configuration/enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59356,6 +62499,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59365,18 +62510,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was created. - */ "branch-protection-rule/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59393,6 +62536,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59402,18 +62547,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was deleted. - */ "branch-protection-rule/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59430,6 +62573,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59439,18 +62584,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to branch protection rules. For more information, see "[About protected branches](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the APIs to manage branch protection rules, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#branchprotectionrule) or "[Branch protection](https://docs.github.com/rest/branches/branch-protection)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - * @description A branch protection rule was edited. - */ "branch-protection-rule/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59467,6 +62610,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59476,25 +62621,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run was completed, and a conclusion is available. - */ "check-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59511,6 +62647,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59520,25 +62658,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A new check run was created. - */ "check-run/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59555,6 +62684,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59564,25 +62695,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description A check run completed, and someone requested a followup action that your app provides. Only the GitHub App someone requests to perform an action will receive the `requested_action` payload. For more information, see "[Creating CI tests with the Checks API](https://docs.github.com/developers/apps/guides/creating-ci-tests-with-the-checks-api)." - */ "check-run/requested-action": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59599,6 +62721,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59608,25 +62732,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check run. For information about check runs, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check runs, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checkrun) or "[Check Runs](https://docs.github.com/rest/checks/runs)" in the REST API documentation. - * - * For activity relating to check suites, use the `check-suite` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" repository permission. To receive the `rerequested` and `requested_action` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `created` and `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check run was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run a check run. Only the GitHub App that someone requests to re-run the check will receive the `rerequested` payload. - */ "check-run/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59643,6 +62758,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59652,25 +62769,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description All check runs in a check suite have completed, and a conclusion is available. - */ "check-suite/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59687,6 +62795,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59696,25 +62806,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to run a check suite. By default, check suites are automatically created when you create a check run. For more information, see [the GraphQL API documentation for creating a check run](https://docs.github.com/graphql/reference/mutations#createcheckrun) or "[Create a check run](https://docs.github.com/rest/checks/runs#create-a-check-run)" in the REST API documentation. - */ "check-suite/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59731,6 +62832,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59740,25 +62843,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a check suite. For information about check suites, see "[Getting started with the Checks API](https://docs.github.com/rest/guides/getting-started-with-the-checks-api)." For information about the APIs to manage check suites, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#checksuite) or "[Check Suites](https://docs.github.com/rest/checks/suites)" in the REST API documentation. - * - * For activity relating to check runs, use the `check_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Checks" permission. To receive the `requested` and `rerequested` event types, the app must have at least write-level access for the "Checks" permission. GitHub Apps with write-level access for the "Checks" permission are automatically subscribed to this webhook event. - * - * Repository and organization webhooks only receive payloads for the `completed` event types in repositories. - * - * > [!NOTE] - * > The API only looks for pushes in the repository where the check suite was created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`. - * @description Someone requested to re-run the check runs in a check suite. For more information, see [the GraphQL API documentation for creating a check suite](https://docs.github.com/graphql/reference/mutations#createchecksuite) or "[Create a check suite](https://docs.github.com/rest/checks/suites#create-a-check-suite)" in the REST API documentation. - */ "check-suite/rerequested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59775,6 +62869,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59784,18 +62880,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously created code scanning alert appeared in another branch. This can happen when a branch is merged into or created from a branch with a pre-existing code scanning alert. - */ "code-scanning-alert/appeared-in-branch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59812,6 +62906,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59821,18 +62917,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone closed a code scanning alert. - */ "code-scanning-alert/closed-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59849,6 +62943,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59858,18 +62954,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was created in a repository. - */ "code-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59886,6 +62980,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59895,18 +62991,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A code scanning alert was fixed in a branch by a commit. - */ "code-scanning-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59923,6 +63017,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59932,18 +63028,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description A previously fixed code scanning alert reappeared in a branch. - */ "code-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59960,6 +63054,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -59969,18 +63065,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to code scanning alerts in a repository. For more information, see "[About code scanning](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About code scanning alerts](https://docs.github.com/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)." For information about the API to manage code scanning, see "[Code scanning](https://docs.github.com/rest/code-scanning)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Code scanning alerts" repository permission. - * @description Someone reopened a code scanning alert. - */ "code-scanning-alert/reopened-by-user": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -59997,6 +63091,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60006,20 +63102,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to commit comments. For more information about commit comments, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)." For information about the APIs to manage commit comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#commitcomment) or "[Commit comments](https://docs.github.com/rest/commits/comments)" in the REST API documentation. - * - * For activity relating to comments on pull request reviews, use the `pull_request_review_comment` event. For activity relating to issue comments, use the `issue_comment` event. For activity relating to discussion comments, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description Someone commented on a commit. - */ "commit-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60036,6 +63128,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60045,21 +63139,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is created. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * **Notes**: - * - This event will not occur when more than three tags are created at once. - * - Payloads are capped at 25 MB. If an event generates a larger payload, GitHub will not deliver a payload for that webhook event. This may happen, for example, if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. - */ create: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60076,6 +63165,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60085,20 +63176,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a custom property. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description A new custom property was created. - */ "custom-property/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60115,6 +63202,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60124,20 +63213,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a custom property. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description A custom property was deleted. - */ "custom-property/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60154,6 +63239,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60163,20 +63250,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a custom property. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties, see "[Custom properties](https://docs.github.com/rest/orgs/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description A custom property was updated. - */ "custom-property/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60193,6 +63276,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60202,20 +63287,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to custom property values for a repository. - * - * For more information, see "[Managing custom properties for repositories in your organization](https://docs.github.com/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)". For information about the APIs to manage custom properties for a repository, see "[Custom properties](https://docs.github.com/rest/repos/custom-properties)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Custom properties" organization permission. - * @description The custom property values of a repository were updated. - */ "custom-property-values/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60232,6 +63313,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60241,21 +63324,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a Git branch or tag is deleted. To subscribe to all pushes to a repository, including - * branch and tag deletions, use the [`push`](#push) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > This event will not occur when more than three tags are deleted at once. - */ delete: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60272,6 +63350,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60281,23 +63361,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was automatically closed by a Dependabot auto-triage rule. - */ "dependabot-alert/auto-dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60314,6 +63387,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60323,23 +63398,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert, that had been automatically closed by a Dependabot auto-triage rule, was automatically reopened because the alert metadata or rule changed. - */ "dependabot-alert/auto-reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60356,6 +63424,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60365,23 +63435,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency, or a GitHub Security Advisory was published and an existing dependency was found to be vulnerable. - */ "dependabot-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60398,6 +63461,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60407,23 +63472,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually closed. - */ "dependabot-alert/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60440,6 +63498,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60449,23 +63509,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change removed a vulnerability. - */ "dependabot-alert/fixed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60482,6 +63535,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60491,23 +63546,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A manifest file change introduced a vulnerable dependency that had previously been fixed. - */ "dependabot-alert/reintroduced": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60524,6 +63572,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60533,23 +63583,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to Dependabot alerts. - * - * For more information about Dependabot alerts, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." For information about the API to manage Dependabot alerts, see "[Dependabot alerts](https://docs.github.com/rest/dependabot/alerts)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Dependabot alerts" repository permission. - * - * > [!NOTE] - * > Webhook events for Dependabot alerts are currently in beta and subject to change. - * @description A Dependabot alert was manually reopened. - */ "dependabot-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60566,6 +63609,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60575,18 +63620,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was created. - */ "deploy-key/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60603,6 +63646,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60612,18 +63657,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deploy keys. For more information, see "[Managing deploy keys](https://docs.github.com/developers/overview/managing-deploy-keys)." For information about the APIs to manage deploy keys, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deploykey) or "[Deploy keys](https://docs.github.com/rest/deploy-keys)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deploy key was deleted. - */ "deploy-key/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60640,6 +63683,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60649,20 +63694,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployments. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment status, use the `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment was created. - */ "deployment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60679,6 +63720,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60688,18 +63731,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment protection rules. For more information, see "[Using environments for deployment](https://docs.github.com/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." For information about the API to manage deployment protection rules, see [the REST API documentation](https://docs.github.com/rest/deployments/environments). - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment protection rule was requested for an environment. - */ "deployment-protection-rule/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60716,6 +63757,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60725,20 +63768,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was approved. - */ "deployment-review/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60755,6 +63794,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60764,20 +63805,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was rejected. - */ "deployment-review/rejected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60794,6 +63831,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60803,20 +63842,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment reviews. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation or deployment status, use the `deployment` or `deployment_status` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * @description A deployment review was requested. - */ "deployment-review/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60833,6 +63868,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60842,23 +63879,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to deployment statuses. For more information, see "[About deployments](https://docs.github.com/actions/deployment/about-deployments)." For information about the APIs to manage deployments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#deployment) or "[Deployments](https://docs.github.com/rest/deployments/deployments)" in the REST API documentation. - * - * For activity relating to deployment creation, use the `deployment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Deployments" repository permission. - * - * > [!NOTE] - * > A webhook event is not fired for deployment statuses with an `inactive` state. - * @description A new deployment status was created. - */ "deployment-status/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60875,6 +63905,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60884,23 +63916,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was marked as the answer. - */ "discussion/answered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60917,6 +63942,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60926,23 +63953,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The category of a discussion was changed. - */ "discussion/category-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -60959,6 +63979,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -60968,23 +63990,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was closed. - */ "discussion/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61001,6 +64016,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61010,23 +64027,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was created. - */ "discussion-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61043,6 +64053,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61052,23 +64064,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was deleted. - */ "discussion-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61085,6 +64090,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61094,23 +64101,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a discussion as opposed to comments on a discussion, use the `discussion` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on a discussion was edited. - */ "discussion-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61127,6 +64127,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61136,23 +64138,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was created. - */ "discussion/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61169,6 +64164,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61178,23 +64175,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was deleted. - */ "discussion/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61211,6 +64201,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61220,23 +64212,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description The title or body on a discussion was edited, or the category of the discussion was changed. - */ "discussion/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61253,6 +64238,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61262,23 +64249,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was added to a discussion. - */ "discussion/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61295,6 +64275,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61304,23 +64286,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was locked. - */ "discussion/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61337,6 +64312,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61346,23 +64323,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was pinned. - */ "discussion/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61379,6 +64349,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61388,23 +64360,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was reopened. - */ "discussion/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61421,6 +64386,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61430,23 +64397,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was transferred to another repository. - */ "discussion/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61463,6 +64423,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61472,23 +64434,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A comment on the discussion was unmarked as the answer. - */ "discussion/unanswered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61505,6 +64460,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61514,23 +64471,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A label was removed from a discussion. - */ "discussion/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61547,6 +64497,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61556,23 +64508,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unlocked. - */ "discussion/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61589,6 +64534,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61598,23 +64545,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a discussion. For more information about discussions, see "[GitHub Discussions](https://docs.github.com/discussions)." For information about the API to manage discussions, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#discussion). - * - * For activity relating to a comment on a discussion, use the `discussion_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Discussions" repository permission. - * - * > [!NOTE] - * > Webhook events for GitHub Discussions are currently in beta and subject to change. - * @description A discussion was unpinned. - */ "discussion/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61631,6 +64571,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61640,17 +64582,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone forks a repository. For more information, see "[Fork a repo](https://docs.github.com/get-started/quickstart/fork-a-repo)." For information about the API to manage forks, see "[Forks](https://docs.github.com/rest/repos/forks)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ fork: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61667,6 +64608,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61676,20 +64619,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a user revokes their authorization of a GitHub App. For more information, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the API to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * - * A GitHub App receives this webhook by default and cannot unsubscribe from this event. - * - * Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error. For details about requests with a user access token, which require GitHub App authorization, see "[Authenticating with a GitHub App on behalf of a user](https://docs.github.com/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." - * @description Someone revoked their authorization of a GitHub App. - */ "github-app-authorization/revoked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61706,6 +64645,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61715,17 +64656,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when someone creates or updates a wiki page. For more information, see "[About wikis](https://docs.github.com/communities/documenting-your-project-with-wikis/about-wikis)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ gollum: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61742,6 +64682,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61751,18 +64693,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description Someone installed a GitHub App on a user or organization account. - */ "installation/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61779,6 +64719,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61788,18 +64730,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description Someone uninstalled a GitHub App from their user or organization account. - */ "installation/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61816,6 +64756,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61825,18 +64767,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description Someone granted new permissions to a GitHub App. - */ "installation/new-permissions-accepted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61853,6 +64793,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61862,18 +64804,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description A GitHub App installation was granted access to one or more repositories. - */ "installation-repositories/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61890,6 +64830,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61899,18 +64841,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to which repositories a GitHub App installation can access. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description Access to one or more repositories was revoked for a GitHub App installation. - */ "installation-repositories/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61927,6 +64867,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61936,18 +64878,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description Someone blocked access by a GitHub App to their user or organization account. - */ "installation/suspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61964,6 +64904,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -61973,16 +64915,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the user or organization account that a GitHub App is installed on. For more information, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description Somebody renamed the user or organization account that a GitHub App is installed on. - */ "installation-target/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -61999,6 +64941,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62008,18 +64952,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub App installation. All GitHub Apps receive this event by default. You cannot manually subscribe to this event. - * - * For more information about GitHub Apps, see "[About apps](https://docs.github.com/developers/apps/getting-started-with-apps/about-apps#about-github-apps)." For information about the APIs to manage GitHub Apps, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#app) or "[Apps](https://docs.github.com/rest/apps)" in the REST API documentation. - * @description A GitHub App that was blocked from accessing a user or organization account was given access the account again. - */ "installation/unsuspend": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62036,6 +64978,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62045,20 +64989,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was created. - */ "issue-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62075,6 +65015,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62084,20 +65026,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was deleted. - */ "issue-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62114,6 +65052,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62123,20 +65063,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment on an issue or pull request. For more information about issues and pull requests, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)" and "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage issue comments, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issuecomment) or "[Issue comments](https://docs.github.com/rest/issues/comments)" in the REST API documentation. - * - * For activity relating to an issue as opposed to comments on an issue, use the `issue` event. For activity related to pull request reviews or pull request review comments, use the `pull_request_review` or `pull_request_review_comment` events. For more information about the different types of pull request comments, see "[Working with comments](https://docs.github.com/rest/guides/working-with-comments)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A comment on an issue or pull request was edited. - */ "issue-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62153,6 +65089,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62162,20 +65100,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was assigned to a user. - */ "issues/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62192,6 +65126,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62201,20 +65137,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was closed. - */ "issues/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62231,6 +65163,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62240,20 +65174,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was deleted. - */ "issues/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62270,6 +65200,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62279,20 +65211,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was removed from a milestone. - */ "issues/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62309,6 +65237,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62318,20 +65248,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description The title or body on an issue was edited. - */ "issues/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62348,6 +65274,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62357,20 +65285,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was added to an issue. - */ "issues/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62387,6 +65311,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62396,20 +65322,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62426,6 +65348,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62435,20 +65359,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was added to a milestone. - */ "issues/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62465,6 +65385,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62474,20 +65396,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was created. When a closed issue is reopened, the action will be `reopened` instead. - */ "issues/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62504,6 +65422,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62513,20 +65433,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/pinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62543,6 +65459,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62552,20 +65470,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A closed issue was reopened. - */ "issues/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62582,6 +65496,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62591,20 +65507,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](https://docs.github.com/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)." - */ "issues/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62621,6 +65533,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62630,20 +65544,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A user was unassigned from an issue. - */ "issues/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62660,6 +65570,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62669,20 +65581,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description A label was removed from an issue. - */ "issues/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62699,6 +65607,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62708,20 +65618,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description Conversation on an issue was locked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." - */ "issues/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62738,6 +65644,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62747,20 +65655,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an issue. For more information about issues, see "[About issues](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues)." For information about the APIs to manage issues, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#issue) or "[Issues](https://docs.github.com/rest/issues)" in the REST API documentation. - * - * For activity relating to a comment on an issue, use the `issue_comment` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permission. - * @description An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](https://docs.github.com/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)." - */ "issues/unpinned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62777,6 +65681,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62786,20 +65692,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#label) or "[Labels](https://docs.github.com/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was created. - */ "label/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62816,6 +65718,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62825,20 +65729,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#label) or "[Labels](https://docs.github.com/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label was deleted. - */ "label/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62855,6 +65755,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62864,20 +65766,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to labels. For more information, see "[Managing labels](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the APIs to manage labels, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#label) or "[Labels](https://docs.github.com/rest/issues/labels)" in the REST API documentation. - * - * If you want to receive an event when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` action type for the `issues`, `pull_request`, or `discussion` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A label's name, description, or color was changed. - */ "label/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62894,6 +65792,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62903,16 +65803,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. - * @description Someone cancelled a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. - */ "marketplace-purchase/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62929,6 +65829,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62938,16 +65840,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. - * @description Someone upgraded or downgraded a GitHub Marketplace plan, and the last billing cycle has ended. The change will take effect on the account immediately. - */ "marketplace-purchase/changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62964,6 +65866,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -62973,16 +65877,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. - * @description Someone downgraded or cancelled a GitHub Marketplace plan. The new plan or cancellation will take effect at the end of the current billing cycle. When the change takes effect, the `changed` or `cancelled` event will be sent. - */ "marketplace-purchase/pending-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -62999,6 +65903,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63008,16 +65914,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. - * @description Someone cancelled a pending change to a GitHub Marketplace plan. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle. - */ "marketplace-purchase/pending-change-cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63034,6 +65940,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63043,16 +65951,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a GitHub Marketplace purchase. For more information, see "[GitHub Marketplace](https://docs.github.com/marketplace)." For information about the APIs to manage GitHub Marketplace listings, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#marketplacelisting) or "[GitHub Marketplace](https://docs.github.com/rest/apps/marketplace)" in the REST API documentation. - * @description Someone purchased a GitHub Marketplace plan. The change will take effect on the account immediately. - */ "marketplace-purchase/purchased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63069,6 +65977,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63078,18 +65988,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A GitHub user accepted an invitation to a repository. - */ "member/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63106,6 +66014,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63115,18 +66025,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description Permissions were changed for a collaborator on a repository. - */ "member/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63143,6 +66051,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63152,18 +66062,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to collaborators in a repository. For more information, see "[Adding outside collaborators to repositories in your organization](https://docs.github.com/organizations/managing-user-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." For more information about the API to manage repository collaborators, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#repositorycollaboratorconnection) or "[Collaborators](https://docs.github.com/rest/collaborators/collaborators)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A collaborator was removed from a repository. - */ "member/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63180,6 +66088,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63189,18 +66099,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#team) or "[Team members](https://docs.github.com/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was added to a team. - */ "membership/added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63217,6 +66125,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63226,18 +66136,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to team membership. For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." For more information about the APIs to manage team memberships, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#team) or "[Team members](https://docs.github.com/rest/teams/members)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization member was removed from a team. - */ "membership/removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63254,6 +66162,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63263,20 +66173,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. - * @description Status checks were requested for a merge group. This happens when a merge group is created or added to by the merge queue because a pull request was queued. - * - * When you receive this event, you should perform checks on the head SHA and report status back using check runs or commit statuses. - */ "merge-group/checks-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63293,6 +66199,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63302,20 +66210,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a merge group in a merge queue. For more information, see "[Managing a merge queue](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Merge queues" repository permission. - * @description The merge queue groups pull requests together to be merged. This event indicates that one of those merge groups was destroyed. This happens when a pull request is removed from the queue: any group containing that pull request is also destroyed. - * - * When you receive this event, you may want to cancel any checks that are running on the head SHA to avoid wasting computing resources on a merge group that will not be used. - */ "merge-group/destroyed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63332,6 +66236,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63341,18 +66247,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a webhook itself. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Meta" app permission. - * @description The webhook was deleted. - */ "meta/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63369,6 +66273,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63378,20 +66284,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was closed. - */ "milestone/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63408,6 +66310,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63417,20 +66321,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was created. - */ "milestone/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63447,6 +66347,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63456,20 +66358,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was deleted. - */ "milestone/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63486,6 +66384,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63495,20 +66395,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was edited. - */ "milestone/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63525,6 +66421,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63534,20 +66432,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to milestones. For more information, see "[About milestones](https://docs.github.com/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the APIs to manage milestones, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#milestone) or "[Milestones](https://docs.github.com/rest/issues/milestones)" in the REST API documentation. - * - * If you want to receive an event when an issue or pull request is added to or removed from a milestone, use the `milestoned` or `demilestoned` action type for the `issues` or `pull_request` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" or "Pull requests" repository permissions. - * @description A milestone was opened. - */ "milestone/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63564,6 +66458,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63573,20 +66469,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/rest/orgs/blocking)" in the REST API documentation. - * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. - * @description A user was blocked from the organization. - */ "org-block/blocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63603,6 +66495,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63612,20 +66506,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when organization owners or moderators block or unblock a non-member from collaborating on the organization's repositories. For more information, see "[Blocking a user from your organization](https://docs.github.com/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." For information about the APIs to manage blocked users, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#userblockedevent) or "[Blocking users](https://docs.github.com/rest/orgs/blocking)" in the REST API documentation. - * - * If you want to receive an event when members are added or removed from an organization, use the `organization` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" organization permission. - * @description A previously blocked user was unblocked from the organization. - */ "org-block/unblocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63642,6 +66532,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63651,20 +66543,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description An organization was deleted. - */ "organization/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63681,6 +66569,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63690,20 +66580,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member accepted an invitation to join an organization. - */ "organization/member-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63720,6 +66606,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63729,20 +66617,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was invited to join the organization. - */ "organization/member-invited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63759,6 +66643,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63768,20 +66654,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A member was removed from the organization. - */ "organization/member-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63798,6 +66680,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63807,20 +66691,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization and its members. For more information, see "[About organizations](https://docs.github.com/organizations/collaborating-with-groups-in-organizations/about-organizations)." For information about the APIs to manage organizations, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#organization) or "[Organizations](https://docs.github.com/rest/orgs)" in the REST API documentation. - * - * If you want to receive an event when a non-member is blocked or unblocked from an organization, use the `org_block` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name of an organization was changed. - */ "organization/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63837,6 +66717,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63846,18 +66728,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A package was published to a registry. - */ "package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63874,6 +66754,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63883,18 +66765,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * @description A previously published package was updated. - */ "package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63911,6 +66791,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63920,17 +66802,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is an attempted build of a GitHub Pages site. This event occurs regardless of whether the build is successful. For more information, see "[Configuring a publishing source for your GitHub Pages site](https://docs.github.com/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." For information about the API to manage GitHub Pages, see "[Pages](https://docs.github.com/rest/pages)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pages" repository permission. - */ "page-build": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63947,6 +66828,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63956,21 +66839,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was approved. - */ "personal-access-token-request/approved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -63987,6 +66865,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -63996,21 +66876,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was cancelled by the requester. - */ "personal-access-token-request/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64027,6 +66902,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64036,21 +66913,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was created. - */ "personal-access-token-request/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64067,6 +66939,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64076,21 +66950,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a request for a fine-grained personal access token to access resources that belong to a resource owner that requires approval for token access. For more information, see "[Creating a personal access token](https://docs.github.com/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Personal access token requests" organization permission. - * - * > [!NOTE] - * > Fine-grained PATs are in public beta. Related APIs, events, and functionality are subject to change. - * @description A fine-grained personal access token request was denied. - */ "personal-access-token-request/denied": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64107,6 +66976,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64116,13 +66987,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when you create a new webhook. The ping event is a confirmation from GitHub that you configured the webhook correctly. */ ping: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64139,6 +67013,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64148,22 +67024,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note in a project (classic) was converted to an issue. - */ "project-card/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64180,6 +67050,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64189,22 +67061,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card was added to a project (classic). - */ "project-card/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64221,6 +67087,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64230,22 +67098,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was deleted. - */ "project-card/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64262,6 +67124,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64271,22 +67135,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A note on a project (classic) was edited. - */ "project-card/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64303,6 +67161,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64312,22 +67172,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a card on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a column on a project (classic), use the `project` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A card on a project (classic) was moved to another column or to another position in its column. - */ "project-card/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64344,6 +67198,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64353,22 +67209,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64385,6 +67235,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64394,22 +67246,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was added to a project (classic). - */ "project-column/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64426,6 +67272,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64435,22 +67283,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was deleted from a project (classic). - */ "project-column/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64467,6 +67309,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64476,22 +67320,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name of a column on a project (classic) was changed. - */ "project-column/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64508,6 +67346,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64517,22 +67357,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a column on a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a project (classic) or a card on a project (classic), use the `project` and `project_card` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A column was moved to a new position on a project (classic). - */ "project-column/moved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64549,6 +67383,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64558,22 +67394,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was created. - */ "project/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64590,6 +67420,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64599,22 +67431,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was deleted. - */ "project/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64631,6 +67457,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64640,22 +67468,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description The name or description of a project (classic) was changed. - */ "project/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64672,6 +67494,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64681,22 +67505,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a project (classic). For more information, see "[About projects (classic)](https://docs.github.com/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the API to manage classic projects, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#project) or "[Projects (classic)](https://docs.github.com/rest/projects)" in the REST API documentation. - * - * For activity relating to a card or column on a project (classic), use the `project_card` and `project_column` event. - * - * This event relates to projects (classic) only. For activity relating to the new Projects experience, use the `projects_v2` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" repository or organization permission. - * @description A project (classic) was closed. - */ "project/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64713,6 +67531,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64722,23 +67542,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was closed. - */ "projects-v2/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64755,6 +67568,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64764,23 +67579,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was created. - */ "projects-v2/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64797,6 +67605,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64806,23 +67616,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was deleted. - */ "projects-v2/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64839,6 +67642,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64848,23 +67653,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The title, description, or README of a project in the organization was changed. - */ "projects-v2/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64881,6 +67679,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64890,23 +67690,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item on an organization project was archived. For more information, see "[Archiving items from your project](https://docs.github.com/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64923,6 +67716,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64932,23 +67727,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A draft issue in an organization project was converted to an issue. - */ "projects-v2-item/converted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -64965,6 +67753,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -64974,23 +67764,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was added to a project in the organization. - */ "projects-v2-item/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65007,6 +67790,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65016,23 +67801,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An item was deleted from a project in the organization. - */ "projects-v2-item/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65049,6 +67827,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65058,23 +67838,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The values or state of an item in an organization project were changed. For example, the value of a field was updated, the body of a draft issue was changed, or a draft issue was converted to an issue. - */ "projects-v2-item/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65091,6 +67864,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65100,23 +67875,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description The position of an item in an organization project was changed. For example, an item was moved above or below another item in the table or board layout. - */ "projects-v2-item/reordered": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65133,6 +67901,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65142,23 +67912,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an item on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2item). - * - * For activity relating to a project (instead of an item on a project), use the `projects_v2` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description An archived item on an organization project was restored from the archive. For more information, see "[Archiving items from your project](https://docs.github.com/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)." - */ "projects-v2-item/restored": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65175,6 +67938,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65184,23 +67949,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." For information about the Projects API, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#projectv2). - * - * For activity relating to a item on a project, use the `projects_v2_item` event. For activity relating to Projects (classic), use the `project`, `project_card`, and `project_column` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > Webhook events for projects are currently in beta and subject to change. To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A project in the organization was reopened. - */ "projects-v2/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65217,6 +67975,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65226,23 +67986,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." - * - * For activity relating to a project, use the `projects_v2` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A status update was added to a project in the organization. - */ "projects-v2-status-update/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65259,6 +68012,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65268,23 +68023,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." - * - * For activity relating to a project, use the `projects_v2` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A status update was removed from a project in the organization. - */ "projects-v2-status-update/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65301,6 +68049,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65310,23 +68060,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a status update on an organization-level project. For more information, see "[About Projects](https://docs.github.com/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." - * - * For activity relating to a project, use the `projects_v2` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Projects" organization permission. - * - * > [!NOTE] - * > To share feedback about projects webhooks with GitHub, see the [Projects webhook feedback discussion](https://github.com/orgs/community/discussions/17405). - * @description A status update was edited on a project in the organization. - */ "projects-v2-status-update/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65343,6 +68086,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65352,17 +68097,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when repository visibility changes from private to public. For more information, see "[Setting repository visibility](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - */ public: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65379,6 +68123,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65388,20 +68134,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was assigned to a user. - */ "pull-request/assigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65418,6 +68160,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65427,20 +68171,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was disabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-disabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65457,6 +68197,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65466,20 +68208,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Auto merge was enabled for a pull request. For more information, see "[Automatically merging a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - */ "pull-request/auto-merge-enabled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65496,6 +68234,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65505,20 +68245,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was closed. If `merged` is false in the webhook payload, the pull request was closed with unmerged commits. If `merged` is true in the webhook payload, the pull request was merged. - */ "pull-request/closed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65535,6 +68271,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65544,20 +68282,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/converted-to-draft": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65574,6 +68308,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65583,20 +68319,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from a milestone. - */ "pull-request/demilestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65613,6 +68345,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65622,20 +68356,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was removed from the merge queue. - */ "pull-request/dequeued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65652,6 +68382,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65661,20 +68393,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The title or body of a pull request was edited, or the base branch of a pull request was changed. - */ "pull-request/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65691,6 +68419,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65700,20 +68430,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to the merge queue. - */ "pull-request/enqueued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65730,6 +68456,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65739,20 +68467,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was added to a pull request. - */ "pull-request/labeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65769,6 +68493,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65778,20 +68504,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was locked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/locked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65808,6 +68530,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65817,20 +68541,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was added to a milestone. - */ "pull-request/milestoned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65847,6 +68567,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65856,20 +68578,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request was created - */ "pull-request/opened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65886,6 +68604,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65895,20 +68615,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A draft pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)." - */ "pull-request/ready-for-review": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65925,6 +68641,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65934,20 +68652,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously closed pull request was reopened. - */ "pull-request/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -65964,6 +68678,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -65973,20 +68689,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was created. - */ "pull-request-review-comment/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66003,6 +68715,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66012,20 +68726,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment on a pull request diff was deleted. - */ "pull-request-review-comment/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66042,6 +68752,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66051,20 +68763,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review comment. A pull request review comment is a comment on a pull request's diff. For more information, see "[Commenting on a pull request](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." For information about the APIs to manage pull request review comments, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewcomment) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request comments, or pull request review threads, use the `pull_request_review`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The content of a comment on a pull request diff was changed. - */ "pull-request-review-comment/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66081,6 +68789,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66090,20 +68800,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was dismissed. - */ "pull-request-review/dismissed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66120,6 +68826,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66129,20 +68837,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description The body comment on a pull request review was edited. - */ "pull-request-review/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66159,6 +68863,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66168,20 +68874,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A request for review by a person or team was removed from a pull request. - */ "pull-request/review-request-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66198,6 +68900,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66207,20 +68911,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Review by a person or team was requested for a pull request. For more information, see "[Requesting a pull request review](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." - */ "pull-request/review-requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66237,6 +68937,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66246,20 +68948,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a pull request review. A pull request review is a group of pull request review comments in addition to a body comment and a state. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreview) or "[Pull request reviews](https://docs.github.com/rest/pulls/reviews)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A review on a pull request was submitted. - */ "pull-request-review/submitted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66276,6 +68974,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66285,20 +68985,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A comment thread on a pull request was marked as resolved. - */ "pull-request-review-thread/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66315,6 +69011,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66324,20 +69022,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a comment thread on a pull request. For more information, see "[About pull request reviews](https://docs.github.com/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." For information about the APIs to manage pull request reviews, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequestreviewthread) or "[Pull request review comments](https://docs.github.com/rest/pulls/comments)" in the REST API documentation. - * - * For activity related to pull request review comments, pull request comments, or pull request reviews, use the `pull_request_review_comment`, `issue_comment`, or `pull_request_review` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A previously resolved comment thread on a pull request was marked as unresolved. - */ "pull-request-review-thread/unresolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66354,6 +69048,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66363,20 +69059,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch. - */ "pull-request/synchronize": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66393,6 +69085,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66402,20 +69096,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A user was unassigned from a pull request. - */ "pull-request/unassigned": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66432,6 +69122,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66441,20 +69133,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description A label was removed from a pull request. - */ "pull-request/unlabeled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66471,6 +69159,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66480,20 +69170,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity on a pull request. For more information, see "[About pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)." For information about the APIs to manage pull requests, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#pullrequest) or "[Pulls](https://docs.github.com/rest/pulls/pulls)" in the REST API documentation. - * - * For activity related to pull request reviews, pull request review comments, pull request comments, or pull request review threads, use the `pull_request_review`, `pull_request_review_comment`, `issue_comment`, or `pull_request_review_thread` events instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Pull requests" repository permission. - * @description Conversation on a pull request was unlocked. For more information, see "[Locking conversations](https://docs.github.com/communities/moderating-comments-and-conversations/locking-conversations)." - */ "pull-request/unlocked": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66510,6 +69196,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66519,22 +69207,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is a push to a repository branch. This includes when a commit is pushed, when a commit tag is pushed, - * when a branch is deleted, when a tag is deleted, or when a repository is created from a template. To subscribe to only branch - * and tag deletions, use the [`delete`](#delete) webhook event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * - * > [!NOTE] - * > Events will not be created if more than 5000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once. - */ push: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66551,6 +69233,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66560,21 +69244,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package was published to a registry. - */ "registry-package/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66591,6 +69270,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66600,21 +69281,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to GitHub Packages. For more information, see "[Introduction to GitHub Packages](https://docs.github.com/packages/learn-github-packages/introduction-to-github-packages)." For information about the APIs to manage GitHub Packages, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#package) or "[Packages](https://docs.github.com/rest/packages)" in the REST API documentation. - * - * To install this event on a GitHub App, the app must have at least read-level access for the "Packages" repository permission. - * - * > [!NOTE] - * > GitHub recommends that you use the newer `package` event instead. - * @description A package that was previously published to a registry was updated. - */ "registry-package/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66631,6 +69307,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66640,18 +69318,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A draft was saved, or a release or pre-release was published without previously being saved as a draft. - */ "release/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66668,6 +69344,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66677,18 +69355,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft release was deleted. - */ "release/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66705,6 +69381,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66714,18 +69392,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description The details of a release, pre-release, or draft release were edited. For more information, see "[Managing releases in a repository](https://docs.github.com/repositories/releasing-projects-on-github/managing-releases-in-a-repository#editing-a-release)." - */ "release/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66742,6 +69418,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66751,18 +69429,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was created and identified as a pre-release. A pre-release is a release that is not ready for production and may be unstable. - */ "release/prereleased": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66779,6 +69455,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66788,18 +69466,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release, pre-release, or draft of a release was published. - */ "release/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66816,6 +69492,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66825,18 +69503,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release was published, or a pre-release was changed to a release. - */ "release/released": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66853,6 +69529,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66862,18 +69540,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to releases. For more information, see "[About releases](https://docs.github.com/repositories/releasing-projects-on-github/about-releases)." For information about the APIs to manage releases, see [the GraphQL API documentation](https://docs.github.com/graphql/reference/objects#release) or "[Releases](https://docs.github.com/rest/releases)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - * @description A release or pre-release was unpublished. - */ "release/unpublished": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66890,6 +69566,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66899,18 +69577,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. - * @description A repository security advisory was published. - */ "repository-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66927,6 +69603,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66936,18 +69614,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a repository security advisory. For more information about repository security advisories, see "[About GitHub Security Advisories for repositories](https://docs.github.com/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Repository security advisories" permission. - * @description A private vulnerability report was submitted. - */ "repository-advisory/reported": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -66964,6 +69640,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -66973,18 +69651,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was archived. - */ "repository/archived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67001,6 +69677,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67010,18 +69688,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was created. - */ "repository/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67038,6 +69714,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67047,18 +69725,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A repository was deleted. GitHub Apps and repository webhooks will not receive this event. - */ "repository/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67075,6 +69751,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67084,17 +69762,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub App sends a `POST` request to `/repos/{owner}/{repo}/dispatches`. For more information, see [the REST API documentation for creating a repository dispatch event](https://docs.github.com/rest/repos/repos#create-a-repository-dispatch-event). In the payload, the `action` will be the `event_type` that was specified in the `POST /repos/{owner}/{repo}/dispatches` request body. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "repository-dispatch/sample.collected": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67111,6 +69788,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67120,18 +69799,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The topics, default branch, description, or homepage of a repository was changed. - */ "repository/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67148,6 +69825,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67157,13 +69836,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** This event occurs when a repository is imported to GitHub. For more information, see "[Importing a repository with GitHub Importer](https://docs.github.com/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." For more information about the API to manage imports, see [the REST API documentation](https://docs.github.com/rest/migrations/source-imports). */ "repository-import": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67180,6 +69862,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67189,18 +69873,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `private`. - */ "repository/privatized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67217,6 +69899,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67226,18 +69910,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The visibility of a repository was changed to `public`. - */ "repository/publicized": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67254,6 +69936,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67263,18 +69947,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description The name of a repository was changed. - */ "repository/renamed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67291,6 +69973,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67300,20 +69984,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was created. - */ "repository-ruleset/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67330,6 +70010,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67339,20 +70021,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was deleted. - */ "repository-ruleset/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67369,6 +70047,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67378,20 +70058,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository rulesets. - * For more information about repository rulesets, see "[Managing rulesets](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets)." - * For more information on managing rulesets via the APIs, see [Repository ruleset](https://docs.github.com/graphql/reference/objects#repositoryruleset) in the GraphQL documentation or "[Repository rules](https://docs.github.com/rest/repos/rules)" and "[Organization rules](https://docs.github.com/rest/orgs/rules) in the REST API documentation." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository or organization permission. - * @description A repository ruleset was edited. - */ "repository-ruleset/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67408,6 +70084,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67417,18 +70095,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Ownership of the repository was transferred to a user or organization account. This event is only sent to the account where the ownership is transferred. To receive the `repository.transferred` event, the new owner account must have the GitHub App installed, and the App must be subscribed to "Repository" events. - */ "repository/transferred": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67445,6 +70121,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67454,18 +70132,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repositories. For more information, see "[About repositories](https://docs.github.com/repositories/creating-and-managing-repositories/about-repositories)." For information about the APIs to manage repositories, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#repository) or "[Repositories](https://docs.github.com/rest/repos)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description A previously archived repository was unarchived. - */ "repository/unarchived": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67482,6 +70158,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67491,19 +70169,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was created. - */ "repository-vulnerability-alert/create": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67520,6 +70195,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67529,19 +70206,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was dismissed. - */ "repository-vulnerability-alert/dismiss": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67558,6 +70232,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67567,19 +70243,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A previously dismissed or resolved repository vulnerability alert was reopened. - */ "repository-vulnerability-alert/reopen": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67596,6 +70269,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67605,19 +70280,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a security vulnerability alert in a repository. - * - * > [!WARNING] - * > **Deprecation notice:** This event is deprecated. Use the `dependabot_alert` event instead. - * @description A repository vulnerability alert was marked as resolved. - */ "repository-vulnerability-alert/resolve": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67634,6 +70306,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67643,20 +70317,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was created. - */ "secret-scanning-alert/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67673,6 +70343,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67682,22 +70354,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to the locations of a secret in a secret scanning alert. - * - * For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alerts, use the `secret_scanning_alert` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A new instance of a previously detected secret was detected in a repository, and the location of the secret was added to the existing alert. - */ "secret-scanning-alert-location/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67714,6 +70380,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67723,20 +70391,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A previously closed secret scanning alert was reopened. - */ "secret-scanning-alert/reopened": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67753,6 +70417,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67762,20 +70428,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was closed. - */ "secret-scanning-alert/resolved": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67792,6 +70454,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67801,20 +70465,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a secret scanning alert. For more information about secret scanning, see "[About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)." For information about the API to manage secret scanning alerts, see "[Secret scanning](https://docs.github.com/rest/secret-scanning)" in the REST API documentation. - * - * For activity relating to secret scanning alert locations, use the `secret_scanning_alert_location` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Secret scanning alerts" repository permission. - * @description A secret scanning alert was validated. - */ "secret-scanning-alert/validated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67831,6 +70491,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67840,18 +70502,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A security advisory was published to the GitHub community. - */ "security-advisory/published": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67868,6 +70528,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67877,18 +70539,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description The metadata or description of a security advisory was changed. - */ "security-advisory/updated": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67905,6 +70565,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67914,18 +70576,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a global security advisory that was reviewed by GitHub. A GitHub-reviewed global security advisory provides information about security vulnerabilities or malware that have been mapped to packages in ecosystems we support. For more information about global security advisories, see "[About global security advisories](https://docs.github.com/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-global-security-advisories)." For information about the API to manage security advisories, see [the REST API documentation](https://docs.github.com/rest/security-advisories/global-advisories) or [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#securityadvisory). - * - * GitHub Dependabot alerts are also powered by the security advisory dataset. For more information, see "[About Dependabot alerts](https://docs.github.com/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - * @description A previously published security advisory was withdrawn. - */ "security-advisory/withdrawn": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67942,6 +70602,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67951,17 +70613,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when code security and analysis features are enabled or disabled for a repository. For more information, see "[GitHub security features](https://docs.github.com/code-security/getting-started/github-security-features)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Administration" repository permission. - */ "security-and-analysis": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -67978,6 +70639,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -67987,20 +70650,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsorship was cancelled and the last billing cycle has ended. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/cancelled": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68017,6 +70676,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68026,18 +70687,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor created a sponsorship for a sponsored account. This event occurs once the payment is successfully processed. - */ "sponsorship/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68054,6 +70713,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68063,18 +70724,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A monthly sponsor changed who can see their sponsorship. If you recognize your sponsors publicly, you may want to update your sponsor recognition to reflect the change when this event occurs. - */ "sponsorship/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68091,6 +70750,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68100,20 +70761,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a cancellation for their sponsorship. The cancellation will become effective on their next billing date. - * - * This event is only sent when a recurring (monthly) sponsorship is cancelled; it is not sent for one-time sponsorships. - */ "sponsorship/pending-cancellation": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68130,6 +70787,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68139,18 +70798,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor scheduled a downgrade to a lower sponsorship tier. The new tier will become effective on their next billing date. - */ "sponsorship/pending-tier-change": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68167,6 +70824,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68176,18 +70835,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a sponsorship listing. For more information, see "[About GitHub Sponsors](https://docs.github.com/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." For information about the API to manage sponsors, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#sponsorship). - * - * You can only create a sponsorship webhook on GitHub.com. For more information, see "[Configuring webhooks for events in your sponsored account](https://docs.github.com/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)." - * @description A sponsor changed the tier of their sponsorship and the change has taken effect. If a sponsor upgraded their tier, the change took effect immediately. If a sponsor downgraded their tier, the change took effect at the beginning of the sponsor's next billing cycle. - */ "sponsorship/tier-changed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68204,6 +70861,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68213,18 +70872,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone starred a repository. - */ "star/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68241,6 +70898,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68250,18 +70909,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to repository stars. For more information about stars, see "[Saving repositories with stars](https://docs.github.com/get-started/exploring-projects-on-github/saving-repositories-with-stars)." For information about the APIs to manage stars, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#starredrepositoryconnection) or "[Starring](https://docs.github.com/rest/activity/starring)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone unstarred the repository. - */ "star/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68278,6 +70935,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68287,17 +70946,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. For more information, see "[About status checks](https://docs.github.com/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." For information about the APIs to manage commit statuses, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#status) or "[Commit statuses](https://docs.github.com/rest/commits/statuses)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Commit statuses" repository permission. - */ status: { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68314,6 +70972,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68323,20 +70983,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A parent issue was added to an issue. - */ "sub-issues/parent-issue-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68353,6 +71009,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68362,20 +71020,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A parent issue was removed from an issue. - */ "sub-issues/parent-issue-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68392,6 +71046,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68401,20 +71057,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A sub-issue was added to an issue. - */ "sub-issues/sub-issue-added": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68431,6 +71083,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68440,20 +71094,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to sub-issues. - * - * For activity relating to issues more generally, use the `issues` event instead. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Issues" repository permissions. - * @description A sub-issue was removed from an issue. - */ "sub-issues/sub-issue-removed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68470,6 +71120,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68479,20 +71131,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a team is added to a repository. - * For more information, see "[Managing teams and people with access to your repository](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." - * - * For activity relating to teams, see the `teams` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - */ "team-add": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68509,6 +71157,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68518,19 +71168,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was granted access to a repository. - */ "team/added-to-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68547,6 +71194,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68556,19 +71205,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was created. - */ "team/created": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68585,6 +71231,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68594,19 +71242,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team was deleted. - */ "team/deleted": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68623,6 +71268,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68632,19 +71279,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description The name, description, or visibility of a team was changed. - */ "team/edited": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68661,6 +71305,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68670,19 +71316,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to teams in an organization. - * For more information, see "[About teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams)." - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Members" organization permission. - * @description A team's access to a repository was removed. - */ "team/removed-from-repository": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68699,6 +71342,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68708,18 +71353,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to watching, or subscribing to, a repository. For more information about watching, see "[Managing your subscriptions](https://docs.github.com/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions)." For information about the APIs to manage watching, see "[Watching](https://docs.github.com/rest/activity/watching)" in the REST API documentation. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Metadata" repository permission. - * @description Someone started watching the repository. - */ "watch/started": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68736,6 +71379,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68745,19 +71390,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when a GitHub Actions workflow is manually triggered. For more information, see "[Manually running a workflow](https://docs.github.com/actions/managing-workflow-runs/manually-running-a-workflow)." - * - * For activity relating to workflow runs, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Contents" repository permission. - */ "workflow-dispatch": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68774,6 +71416,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68783,20 +71427,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run finished. This event occurs when a job in a workflow is completed, regardless of whether the job was successful or unsuccessful. - */ "workflow-job/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68813,6 +71453,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68822,20 +71464,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run started processing on a runner. - */ "workflow-job/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68852,6 +71490,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68861,20 +71501,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created. - */ "workflow-job/queued": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68891,6 +71527,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68900,20 +71538,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a job in a GitHub Actions workflow. For more information, see "[Using jobs in a workflow](https://docs.github.com/actions/using-jobs/using-jobs-in-a-workflow)." For information about the API to manage workflow jobs, see "[Workflow jobs](https://docs.github.com/rest/actions/workflow-jobs)" in the REST API documentation. - * - * For activity relating to a workflow run instead of a job in a workflow run, use the `workflow_run` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A job in a workflow run was created and is waiting for approvals. - */ "workflow-job/waiting": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68930,6 +71564,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68939,20 +71575,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run finished. This event occurs when a workflow run is completed, regardless of whether the workflow was successful or unsuccessful. - */ "workflow-run/completed": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -68969,6 +71601,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -68978,20 +71612,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run started processing on a runner. - */ "workflow-run/in-progress": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69008,6 +71638,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69017,20 +71649,16 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; - /** - * This event occurs when there is activity relating to a run of a GitHub Actions workflow. For more information, see "[About workflows](https://docs.github.com/actions/using-workflows/about-workflows)." For information about the APIs to manage workflow runs, see [the GraphQL documentation](https://docs.github.com/graphql/reference/objects#workflowrun) or "[Workflow runs](https://docs.github.com/rest/actions/workflow-runs)" in the REST API documentation. - * - * For activity relating to a job in a workflow run, use the `workflow_job` event. - * - * To subscribe to this event, a GitHub App must have at least read-level access for the "Actions" repository permission. - * @description A workflow run was triggered. - */ "workflow-run/requested": { parameters: { + query?: never; header: { /** @example GitHub-Hookshot/123abc */ "User-Agent": string; @@ -69047,6 +71675,8 @@ export interface operations { /** @example sha256=6dcb09b5b57875f334f61aebed695e2e4193db5e */ "X-Hub-Signature-256": string; }; + path?: never; + cookie?: never; }; requestBody: { content: { @@ -69056,7 +71686,10 @@ export interface operations { responses: { /** @description Return a 200 status to indicate that the data was received successfully */ 200: { - content: never; + headers: { + [name: string]: unknown; + }; + content?: never; }; }; }; diff --git a/scripts/generate-types.js b/scripts/generate-types.js index 3fb9430..b9c2dfc 100644 --- a/scripts/generate-types.js +++ b/scripts/generate-types.js @@ -2,7 +2,8 @@ import { readdir, mkdir, rm, writeFile, copyFile } from "node:fs/promises"; import { basename } from "node:path"; import * as prettier from "prettier"; -import openapiTS from "openapi-typescript"; +import openapiTS, { astToString, COMMENT_HEADER } from "openapi-typescript"; +import { pathToFileURL } from "node:url"; /* (!process.env.OCTOKIT_OPENAPI_VERSION) { throw new Error("OCTOKIT_OPENAPI_VERSION is not set"); @@ -88,7 +89,13 @@ type Repository = components["schemas"]["full-repository"] await writeFile( `packages/${packageName}/types.d.ts`, await prettier.format( - await openapiTS(`packages/openapi-webhooks/generated/${name}.json`), + COMMENT_HEADER + + astToString( + await openapiTS( + pathToFileURL(`packages/openapi-webhooks/generated/${name}.json`), + { defaultNonNullable: false }, + ), + ), { parser: "typescript", },